Article View: comp.sys.sun
Article #13757statd
From: Dale R. Wyttenbach
Date: Mon, 12 Feb 1990 07:14
Date: Mon, 12 Feb 1990 07:14
13 lines
1021 bytes
1021 bytes
rpc.statd: Cannot talk to statd at CLIENTNAME Does anyone else have this problem with Sun 4/60 (SS-1) disk servers? This message repeats itself on the console for as long as the client is down, i.e. indefinitely. What's worse, the message needs a '\n'. It seems to me that servers shouldn't be dependent on their clients, but then again I don't work for sun. Any hints on getting statd to calm down appreciated. Dale Wyttenbach | ...rutgers!umn-cs!wytten wytten@cs.umn.edu | wytten@umnacvx.bitnet Computer Science Department Systems Staff--University of Minnesota, Minneapolis
Technical Details
Message-ID:
<4945@brazos.Rice.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-requestShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request From: local!wytten@cs.umn.edu (Dale R. Wyttenbach) Newsgroups: comp.sys.sun Subject: statd Keywords: SunOS Message-ID: <4945@brazos.Rice.edu> Date: 12 Feb 90 07:14:16 GMT Sender: root@rice.edu Organization: Sun-Spots Lines: 13 Approved: Sun-Spots@rice.edu X-Sun-Spots-Digest: Volume 9, Issue 41, message 7