[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#49816: sysvinit shouldn't remove /var/run/dhcpcd-*.pid at startup



On Thu, Nov 11, 1999 at 07:57:41PM +0100, Miquel van Smoorenburg wrote:
> According to arto.astala@nokia.com:
> > 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).
> 
> No. bootmisc.sh has run at S55 from day one. Then along
> comes dhcpcd and puts its startup file before that. That is
> not a bug in sysvinit.
> 
> bootmisc.sh cannot run before networking is set up because
> /usr and/or /var might be mounted on an NFS filesystem, and
> the network needs to be up for that.
> 
> I'm not fixing any bugs in the dhcpcd package by hacking around in
> the sysvinit package. Fix dhcpcd instead.
> 
> > (in future you may want to cc: the BTS even for mails like
> > this, it ensures that all info is recorded there)
> 
> I never delete Cc:'s, but I've added one now.
> 
We all know we need dhcpd to get the network
We know that bootmisc needs a network to do its job
Why not tell bootmisc.sh to only delete files older than the current uptime?

Frank aka Myth


Reply to: