The original bug report says: Since `dhcpcd' is executed at startup (in /etc/init.d/dhcpcd or /etc/init.d/networking) before /etc/init.d/bootmisc.sh, these files are removed during bootmisc.sh. So the problem is that perfectly valid startup of dhcpcd is later screwed up by bootmisc.sh which deletes the pid file(s). Either the order is wrong or bootmisc.sh should not delete the pid files (when dhcpcd is running).
(in future you may want to cc: the BTS even for mails like this, it ensures that all info is recorded there) t.aa Dpk <[EMAIL PROTECTED]> Thu, Nov 11, 1999 3:24 PM > > On Wed, Nov 10, 1999 at 10:49:59PM -0000, Debian Bug Tracking > System wrote: > > Processing commands for [EMAIL PROTECTED]: > > > reassign 49816 dhcpcd > Bug#49816: sysvinit shouldn't remove /var/run/dhcpcd-*.pid > at startup > Bug reassigned from package `sysvinit' to `dhcpcd'. > > > thanks > Stopping processing here. > > Please contact me if you need assistance. > > Actually I don't think I can change this behavior at this point. This > was put in place because upon bootup (or execution of the init > script), dhcpcd will fail to start if the pid file exists. > > The pid file is only removed if dhcpcd is not running. This is merely > a sanity check (it is logical that if dhcpcd is not running the pid > file should not exist) and it fixes the bug that causes dhcpcd to fail > if the file exists. > > Being a fairly new developer, I ask out of ignorance not out of spite, > but should this even be considered a bug? I admit that I have only > read policy, not memorized it!
