NFS problems with sequent

Article View: comp.sys.sequent

Article #166

#166

From: Jeffrey Goh
Date: Sat, 14 Oct 1989 07:01

18 lines
1224 bytes

Damn, all the messages have expired, and I didn't save any.
What was the consensus (if any) about the NFS problems ?
We've had the ubiquitous "NFS server <..> not responding"
message all too often lately.  Initially, we thought
that it was because the sequent was on the other end of a fibre-optic
bridge between buildings, but even after we'd moved the machine,
we still get the messages.

We've asked the systems support people to look into it, but they've
had no luck ... all they've been able to tell us is that there's 
strange stuff floating about our ethernet (no kidding ...) 
but they can't pinpoint which host is spewing the crud out ...
even with a "sniffer".  

Should I give up and call for sequent tech-support ?   or is
there a better (quick & dirty) way ?

- jeff

Technical Details

Message-ID: <18375@pasteur.Berkeley.EDU>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!postgres.Berkeley.EDU!goh

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!postgres.Berkeley.EDU!goh
From: goh@postgres.Berkeley.EDU (Jeffrey Goh)
Newsgroups: comp.sys.sequent
Subject: NFS problems with sequent
Message-ID: <18375@pasteur.Berkeley.EDU>
Date: 14 Oct 89 07:01:14 GMT
Sender: news@pasteur.Berkeley.EDU
Reply-To: goh@postgres.Berkeley.EDU (Jeffrey Goh)
Organization: Postgres Research Group, UC Berkeley
Lines: 18