From: Seb James <seb@peak.uklinux.net>
To: NFS Mailing list <nfs@lists.sourceforge.net>
Subject: Re: NFS (and NIS) client causes server to semi-hang
Date: 12 Jun 2003 12:44:48 +0100 [thread overview]
Message-ID: <1055418287.1984.38.camel@circle.hypercube> (raw)
In-Reply-To: <1055413060.1984.34.camel@circle.hypercube>
On Thu, 2003-06-12 at 11:17, Seb James wrote:
> Hello,
>
> I've come across a rather worrying problem.
[ snip ]
> Does anyone have any ideas?
>
> Also, is there a suitable NIS related list to post this message to, as I
> think it's relevant for that, too.
Fixed: darius was not listed in the /etc/hosts.allow file. However, it
doesn't seem right that such a problem should lead to the server
freezing up in the way that it did.
Cheers,
Seb.
--
Seb James <seb@peak.uklinux.net>
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-06-12 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 10:17 NFS (and NIS) client causes server to semi-hang Seb James
2003-06-12 11:44 ` Seb James [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1055418287.1984.38.camel@circle.hypercube \
--to=seb@peak.uklinux.net \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox