Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!cornell!uw-beaver!rice!sun-spots-request
From: rlk@think.com (Robert L. Krawitz)
Newsgroups: comp.sys.sun
Subject: nfsd going crazy
Keywords: Networks
Message-ID: <3787@kalliope.rice.edu>
Date: 3 Jun 89 04:32:28 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 25, message 3 of 7

One of your clients has something running hard, very likely in an infinite
loop.  We had a server (4/280) that for a month was running very slowly
(no one particularly complained, at least not in earshot of me).  I
finally took a look at the situation, and discovered that a 3/140 had a
csh that had been looping all that time.

Unfortunately, tcpdump doesn't work on 4.0; that was (still is on our two
servers still running 3.5) a really useful tool for things like this.
Modulo that, you have to play around with netstat -r, rup, and other
random tools of that nature.

ames >>>>>>>>>  |	Robert Krawitz <rlk@think.com>	245 First St.
bloom-beacon >  |think!rlk				Cambridge, MA  02142
harvard >>>>>>  .	Thinking Machines Corp.		(617)876-1111