Date: Wed, 3 Oct 2001 10:58:16 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Thyer, Matthew" <Matthew.Thyer@dsto.defence.gov.au> Cc: "Brandon D. Valentine" <bandix@looksharp.net>, current@freebsd.org Subject: Re: NIS client performance seems very poor under network load Message-ID: <15291.10120.604882.602699@grasshopper.cs.duke.edu> In-Reply-To: <3BBAD3F3.241A1FEE@dsto.defence.gov.au> References: <20010928022500.I24843-100000@turtle.looksharp.net> <3BBAD3F3.241A1FEE@dsto.defence.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Thyer, Matthew writes: > > Now xterm 1 has the message "yp_first: clnt_call: RPC: Timed out" > as its first line and xterm 2 has two of these messages. What's really fun is when you've got a rack or two of machines which are NIS clients and their switch blows out overnight. As soon as they regain network connectivity, they'll try to melt your mailserver down. Why? Because cron is going to send mail to root, bitching about "yp_first: clnt_call: RPC: Timed out" every 5 minutes (from atrun). For one rack of 1Us, that's an accumulation of at least 504msgs per hour (actually, its a lot more) > So I'd like to do a little bit of investigation and was wonderring > if other people have some insight as to where to look. The problem is that there is no global caching of NIS maps. Each app maintains its own cache.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15291.10120.604882.602699>