The last note on this bug requests an strace of what ifup is doing.
Since no-one else has done it I thought I would.
Two possible facts to record here first:
1) The problem does not manifest itself on a Sarge diskless system.
There you can run "ifup -a" as much as you like without losing the
connection.
2) The problem only manifests itself if the relevant link is configured
to use dhcp. If you give it a static address in /etc/network/interfaces
then you get an error message ("File exists") but the link isn't lost
and the system continues to run. However the fact that the link is up
still isn't recorded in /etc/network/run/ifstate.
Anyway - the step which causes the problem doesn't seem to be within
ifup itself at all. The last thing which it does before the link goes
down is to invoke "dhclient". Presumably the actual killing of the link
is happening there. It's notable that the default dhcp changed to
version 3 in Etch so this may be where the change happened.
I'm not sure whether the test for the link already being up should be
added to ifup or dhclient - perhaps this bug record needs redirecting again?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
