Date: Fri, 8 Dec 2000 11:56:06 -0500 From: Brian Reichert <reichert@numachi.com> To: freebsd-net@freebsd.org Subject: cron messages: yp_next: clnt_call: RPC: Timed out Message-ID: <20001208115606.B31578@numachi.com>
next in thread | raw e-mail | index | archive | help
I asked this quesion on -isp, but there were no takers. Maybe
someone here has some insight...
----- Forwarded message from Brian Reichert <reichert@numachi.com> -----
Date: Fri, 1 Dec 2000 13:23:37 -0500
From: Brian Reichert <reichert@numachi.com>
To: freebsd-isp@freebsd.org
Subject: cron messages: yp_next: clnt_call: RPC: Timed out
Under FreeBSD 3.4-R, under a NIS client environment, I cannot seem
to keep cron messages quiet. Harmless things like 'atrun' generate
mail:
From root Fri Dec 1 02:00:10 2000
Return-Path: <root>
Received: (from root@localhost)
by private.internal.mydomain.com (8.9.3/8.9.3) id CAA75601;
Fri, 1 Dec 2000 02:00:10 GMT
(envelope-from root)
Date: Fri, 1 Dec 2000 02:00:10 GMT
Message-Id: <200012010200.CAA75601@private.internal.mydomain.com>
From: root (Cron Daemon)
To: root
Subject: Cron <root@private> /usr/libexec/atrun
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
yp_next: clnt_call: RPC: Timed out
(I've obfuscated the hostnames.)
On this machine, root is a local account, not an NIS account.
The NIS server is
nis1% uname -a
SunOS nis1 5.7 Generic_106542-04 i86pc i386 i86pc
Does anyone have any advice on this matter?
--
Brian 'you Bastard' Reichert <reichert@numachi.com>
37 Crystal Ave. #303 Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001208115606.B31578>