Question regarding snoop behavior.

From: Andres Rojas (arojasm@adexus.cl)
Date: Mon Jul 28 2003 - 20:24:52 EDT


Dear Sun Managers,

May be it's not a snoop problem but appeared when I was running this
utility to catch a network problem.

I was using snoop over the hme interface and logging the output to a file.
When the filesystem became nearly to 100% I attempted to kill the snoop
process but I had no answer. There were three snoop processes running to
log the results for three IP addresses. I was unable to kill any of these
processes. There was simply no answer and keep filling the filesystem up.
BTW the processes were launched with nohup and in the background to prevent
accidental terminations. During the past week this procedure (for blanking
log files) worked nicely until now.

Any attempt to blank the file result in a hanging of the command issued.
Same thing to vi the file or ls the directory. Nothing of this happened in
the previous directories. Nothing logged in the messages file.

My only option was to shutdown the system but it hung during the shutdown
sequence. Nothing else to do but a power off.

I'd appreciate if someone could enlight me about such rare behavior. Any
comment, clue or joke is accepted :)

Thank you all,

- Andres.
SCL/cl
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:49 EDT