From owner-freebsd-isp Wed Jul 29 15:06:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10800 for freebsd-isp-outgoing; Wed, 29 Jul 1998 15:06:09 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10772 for ; Wed, 29 Jul 1998 15:06:04 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id RAA09732 for isp@freebsd.org; Wed, 29 Jul 1998 17:05:32 -0500 (CDT) From: Kevin Day Message-Id: <199807292205.RAA09732@home.dragondata.com> Subject: ypserv To: isp@FreeBSD.ORG Date: Wed, 29 Jul 1998 17:05:31 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone else seen this: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 200 root 73 0 964K 1044K RUN 471:15 59.78% 59.78% ypserv 216 root -6 0 228K 12K biowai 284:27 3.05% 3.05% nfsd 9362 root 31 0 864K 988K RUN 0:00 3.40% 2.02% top ypserv seems to randomly start using tons and tons of CPU, then it goes away quietly for a while, then comes back again... Would making the yp clients into slave servers help? If so, has anyone else gotten this to work? All I get is the clients complaining that the servre is 'pulling their leg'... ( i like cute error messages, but only when they actually tell you what to fix. :) ) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message