Hello Joel.  I'm not sure this is a new problem.  I've seen similar
behavior on NetBSD-5.2.  It seems to happen on systems where there is a
good deal of traffic traversing the network at the time the stop is
requested.
-thanks
-Brian

Reply via email to