From owner-freebsd-current Mon May 5 07:58:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA29008 for current-outgoing; Mon, 5 May 1997 07:58:12 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA29001 for ; Mon, 5 May 1997 07:58:07 -0700 (PDT) Received: from gil.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 QAA06803 for ; Mon, 5 May 1997 16:59:03 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id RAA14300 for freebsd-current@freefall.cdrom.com; Mon, 5 May 1997 17:00:55 +0200 (MET DST) Date: Mon, 5 May 1997 17:00:55 +0200 (MET DST) From: Christoph Kukulies Message-Id: <199705051500.RAA14300@gil.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: nis/yp problems Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk After upgrading to 3.0-current I'm getting this on one of my NIS/YP client machines (cron): Date: Mon, 05 May 1997 16:15:00 +0200 (MEST) Subject: Cron /usr/libexec/atrun To: root@mymachine.domain X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: yp_next: clnt_call: RPC: Unable to send; errno = No buffer space available yp_next: clnt_call: RPC: Unable to send; errno = No buffer space available yp_next: clnt_call: RPC: Unable to send; errno = No buffer space available yp_next: clnt_call: RPC: Unable to send; errno = No buffer space available yp_next: clnt_call: RPC: Unable to send; errno = No buffer space available yp_next: clnt_call: RPC: Unable to send; errno = No buffer space available -- What could be the cause for this? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de