Comment 16 for bug 6841

Thomas Hood wrote:

>Did the "ifdown lo ; ifup lo" trick work?
>
>
You mean the "ifdown -a ; ifup lo" trick?

It does not work. I was pretty sure of that, but I now
tested it because you asked again, and it did not help.

The problem is _not_ that "lo" is closed thereby confusing programs
that expect "lo" to work.

The problem is that "ifdown -a" waits forever. The command
never exits, so no further progress is made. Even the
next command in the script (which now is "echo after-ifdown")
never executes. ifdown waits on something that doesn't happen
at all during shutdown. That's why I sent those traces, one showing
normal operation when ifdown happen to work, and another that
show what happens when it hangs (and is killed with CTRL+C)

The hanging ifdown prevents shutdown, and modifying the configuration
to not mess with "lo" gives me a hang at boot time instead.

The only workaround that allows both shutdown and bootup is to
skip ifdown/ifup and bring the network up and down using
"ifconfig" or "ip" directly. But the purpose if ifup/ifdown is
to make things easier . . .

Helge Hafting