Uwe Dippel wrote:
> [i]
>
>> [it got stuck here and won't move any further].
>>
>>
> This problem is caused by unplug wired LAN but not release its IP
> address first, see previous mail..[/i]
>
> I'm sorry, but I have to consider this argument as a joke.
>
I can understand your frustration, but this can help you out of the problem.
> Even if you were 'right', it is considered completely unacceptable that
> unplugging a network cable warrants a system freeze, the failure to list the
> processes and finally the need to hard reset a machine.
> It comes as a surprise that you defend the freeze of a command ('ifconfig
> rum1 unplumb') by pointing to an earlier issued wrong parameter ('ifconfig
> rum1 drop').
> If a command can't complete, because an earlier release of an address failed,
> there is no reason in heaven or on earth for the subsequent command to
> legally freeze. It must indicate this error and exit gracefully.
>
To be clear, it's not rum driver freezes system. Even if you unplug the
wired LAN, but if you don't release its IP, its configuration is still
in system,
you can see this by "netstat -rn", "rge0" still the default gateway
(first one).
When you type a command ('ifconfig rum1 unplumb'), it may cause some
actions like DNS resolv, it will go to "rge0", and wait a long time,
then the command is freezed.
--
Quaker
> I am looking forward to pursue this thread/topic; but not on these arguments.
>
> Uwe
>
