On Wed, Nov 14, 2007 at 05:14:56PM +0000, [EMAIL PROTECTED] wrote: > X-Debbugs-No-Ack: please > X-Debbugs-Cc: [EMAIL PROTECTED] > Package: pdnsd > Version: 1.2.6-par-3 > Severity: wishlist > > Sometimes /var/log/boot looks fine: > > 00:20:03: Cleaning /var/run...done. > 00:20:03: Cleaning /var/lock...done. > 00:20:03: Setting up resolvconf...done. > 00:20:04: Setting up networking.... > 00:20:04: Starting pdnsd. > 00:20:05: Configuring network interfaces...done. > 00:20:05: Initializing random number generator...done. > 00:20:06: INIT: Entering runlevel: 2 > 00:20:06: Starting system log daemon.... > 00:20:06: Starting kernel log daemon.... > 00:20:07: Starting system message bus: dbus. > 00:20:07: Starting internet superserver: inetd. > 00:20:07: Starting pdnsd. > > Except for the repeat of Starting pdnsd. > > However, sometimes it looks not so fine: > > 00:45:29: Cleaning /var/run...done. > 00:45:29: Cleaning /var/lock...done. > 00:45:30: Setting up resolvconf...Error: could not open socket > /var/cache/pdnsd/pdnsd.status: Connection refused > 00:45:30: Error: could not open socket /var/cache/pdnsd/pdnsd.status: > Connection refused > 00:45:30: done. > 00:45:31: Setting up networking.... > 00:45:31: Starting pdnsd. > 00:45:31: Configuring network interfaces...done. > 00:45:32: INIT: Entering runlevel: 2 > 00:45:32: Starting system log daemon.... > 00:45:33: Starting kernel log daemon.... > 00:45:33: Starting system message bus: dbus. > 00:45:33: Starting internet superserver: inetd. > 00:45:33: Starting pdnsd. > > Maybe a race condition? Maybe because I had to push the reboot button > that day due to xpdf getting stuck in fullscreen mode...?
The error message is harmless, and yes there is a race, it's because when resolvconf is run the first time, it tries to setup pdnsd as a dns server, and for that it has to ask pdnsd for its configuration to know if it listens on 127.0.0.1 or not, then pdnsd is launched, then networking is set-up which restarts the resolvconf hooks hence configure pdnsd as the dns for the host. The thing is I'm reluctant to hide the pdnsd error because it could hide a real issue. SO yes, it's mostly cosmetic, though I would be happy to have a nicer solution without the boot-time cosmetic issue. and no I cannot start pdnsd _before_ resolvconf because pdnsd init script uses resolvconf, so I need it to be setup properly before me. I should try to make the pdnsd resolvconf hook be silent when we're during boot and that we're still at stage S38. If there is a way to know that reliably, then I can hide the error that is expected (in fact depends on the fact that the machine did a clean reboot or not I believe). -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpt0eXEDMSZ3.pgp
Description: PGP signature
