Does not alert on installing in cron.weekly.

[bahkyp]

Silently installs in cron.weekly then loads machine to +8 for +4 hours and does not allow other CPU tasks. Killed task when I found it running this morning.

If I wanted to index with xapian I would have set it up! Its ok to be in a dependency but not ok to install itself without warning into cron.

Basically the load was because xapian does not function within 32mB of memory.

[Richard Boulton]

I presume this is a result of installing a package using Xapian on some system? This bug tracker is really for bugs in Xapian itself - we have no control of how people use and install Xapian. To have a chance of getting some kind of resolution for this, you need to open a ticket with whatever upstream package caused Xapian to be installed in cron without confirming.

If you let us know which packaging system, operating system etc you're running, we can try and suggest the appropriate place to raise a ticket.

[Olly Betts]

I think you probably want to be file a bug in the apt-xapian-index package at ​http://bugs.debian.org/ instead.

Suitably set up, Xapian should be able to work on a smaller memory system. The default flush threshold will probably be too high, so I'm indexing is likely to start swapping if apt-xapian-index doesn't adjust that threshold.

[Olly Betts]

I managed to accidentally delete the reporter's reply while purging spammer accounts from the trac database. For the record it was:

Yes I never explicitly installed xapian. Its a Debian system, but the reason the wheels spun were it was using more resources than available system memory (max 32 mB) when doing the indexing, you may wish to address this part.

Sorry for the inappropriate .deb bug report.