Bug#516254: closed by Enrico Zini <enrico at debian.org> (Bug#515791: fixed in apt-xapian-index 0.17)

Junichi Uekawa dancer at netfort.gr.jp
Sun Feb 22 16:32:20 UTC 2009


At Sat, 21 Feb 2009 15:18:17 +0000,
Enrico Zini wrote:
> 
> [1  <text/plain; utf-8 (quoted-printable)>]
> On Sat, Feb 21, 2009 at 10:20:40PM +0900, Junichi Uekawa wrote:
> 
> > By the way, why are you starting 
> >   /usr/sbin/update-apt-xapian-index --quiet &
> > in postinst?
> > I think there should be a
> > /etc/init.d/apt-xapian-index
> > which does a daemon control of update-apt-xapian-index (doing pid file
> > etc.)  which is invoked from crontab and postinst, and start it
> > through invoke-rc.d so they can be controlled via policy.
> 
> apt-xapian-index isn't really a daemon: it rebuilds the index and exits.

But it is ran on the background.

I don't really want something running on the background for every
pbuilder invokation if it's not essential.  chroot is going to be
cleaned after apt-get finishes running.


On a side note, if it's being invoked twice in a row for basic
installation, you probably want to do it in triggers.

I assume the reason of this running in background is 

1. no package requires this data from postinst etc.
2. only interactive packages really use this data
3. and user can live with database file up to one week old.

I don't think it's essential to have this information created every
time a chroot is created.  Similar situation to man-db.

> 
> While it's building the index, besides having a lockfile, it also
> listens on a unix domain socket so that if it's run again, the second
> copy can just show the progress of the first one.  This allows a package
> manager to report progress even if an indexer is still running in the
> background.






More information about the Pbuilder-maint mailing list