[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.
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.
I am looking forward to pursue this thread/topic; but not on these arguments.

Uwe
-- 
This message posted from opensolaris.org

Reply via email to