From owner-freebsd-bugs Mon Apr 6 23:20:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29103 for freebsd-bugs-outgoing; Mon, 6 Apr 1998 23:20:05 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29088; Mon, 6 Apr 1998 23:20:04 -0700 (PDT) (envelope-from gnats) 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 XAA28586 for ; Mon, 6 Apr 1998 23:18:38 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id BAA17419; Tue, 7 Apr 1998 01:18:36 -0500 (CDT) Message-Id: <199804070618.BAA17419@home.dragondata.com> Date: Tue, 7 Apr 1998 01:18:36 -0500 (CDT) From: toasty@dragondata.com Reply-To: toasty@dragondata.com To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: bin/6234: ypserv -d is broken Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 6234 >Category: bin >Synopsis: ypserv -d is broken >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 6 23:20:02 PDT 1998 >Last-Modified: >Originator: Kevin Day >Organization: DragonData Internet Services >Release: FreeBSD 2.2.5-STABLE i386 >Environment: 2.2.5 running ypserv >Description: After repeatedly seeing ypserv take 30 - 50% CPU randomly, I decided to run ypserv with the -d option to watch what it was doing... 'ypserv -d' executes, and just sits there not doing anything. Clients report timeout errors trying to talk to the server, and it never dumps anything to syslog or stderr >How-To-Repeat: ypserv -d >Fix: >Audit-Trail: >Unformatted: Kevin Day To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message