Re: Bug#74312: sysvinit: /var/run cleaned too late
On Mon, Oct 09, 2000 at 06:58:16AM +1000, Anthony Towns wrote:
>debian-devel folks: The forthcoming ifupdown release (0.6) uses
>a state file in /var/run to cope with different configuration (it
>will automatically determine that you're at home, say, and setup eth0
>differently to how it might if you were at work; when you tell it to
>down an interface, it'll look up /var/run/ifupdown.state to see what
>commands it needs to run to bring the interface down). Unfortunately,
>the /var/run cleaning up done by sysvinit is done *after* networking is
>initialised. This means, eg, that after a crash, ifupdown will be confused
>about the state of networking because the old /v/r/ifud file will still
>be about, and you'll probably end up with lo and eth0 unconfigured,
>which would be bad.
Why not just handle it in /etc/rcS.d/S40networking?
case "$1" in
start)
[ "$runlevel" = S ] && rm -f /var/run/ifupdown.state
# ...
ifup -a
Regards,
--
Brendan O'Dea bod@compusol.com.au
Compusol Pty. Limited (NSW, Australia) +61 2 9810 3633
Reply to: