On Tue, May 14, 2002 at 07:54:46PM -0700, Chris Tillman wrote: > On Wed, May 15, 2002 at 03:34:37AM +0100, Colin Watson wrote: > > I've just remembered why things are done that way in the first place. > > See #100616, which caused problems for the boot-floppies. I'll see if I > > can come up with some alternative hack which checks whether the > > noninteractive frontend is in use. > > > > However, this won't help you. On fresh installs using debootstrap, mandb > > won't be run either way, and nothing later on will run it. Perhaps > > building the database properly is a job for base-config? > > Hmmm. I always wondered, why couldn't cron be set up to run its daily > job if x days went by without running it, regardless of the time it was > set to run? Or maybe it can. That would take care of this, although not > for a few days on a new install. I guess that's what anacron is supposed > to do. I just got tired of anacron hashing my disk to death every time I > started up. (I actually had a disk fail, too...)
There might be another way. At the time that bug was filed, I thought that DEBIAN_FRONTEND=Noninteractive just meant that the noninteractive frontend was in use, so I discarded the option of running mandb in the foreground if that was set. I now realize that debconf doesn't set that itself, but just pays attention to it when debootstrap does it. This makes running mandb in the foreground a lot more acceptable. I'll change that and see how it goes; easier than changing base-config. :) Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
