From owner-freebsd-questions Mon Sep 30 07:12:57 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA05100 for questions-outgoing; Mon, 30 Sep 1996 07:12:57 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA04940 for ; Mon, 30 Sep 1996 07:12:41 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id PAA28211 for ; Mon, 30 Sep 1996 15:12:57 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id PAA04213 for freebsd-questions@freefall.cdrom.com; Mon, 30 Sep 1996 15:19:12 +0100 Date: Mon, 30 Sep 1996 15:19:12 +0100 From: Christoph Kukulies Message-Id: <199609301419.PAA04213@gilberto.physik.rwth-aachen.de> To: freebsd-questions@freefall.FreeBSD.org Subject: yp_next clnt_call timed out Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm getting these messages sometimes from one NIS client here. Any ideas what might cause them? Date: Mon, 30 Sep 1996 16:45:22 GMT From: root@somehost.somedomain.de (Cron Daemon) To: root@somehost.somedomain.de Subject: Cron /usr/libexec/atrun X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: yp_next: clnt_call: RPC: Timed out --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de