From toasty@home.dragondata.com  Mon Apr  6 23:18:39 1998
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 <FreeBSD-gnats-submit@freebsd.org>; 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
Subject: ypserv -d is broken
X-Send-Pr-Version: 3.2

>Number:         6234
>Category:       bin
>Synopsis:       ypserv -d is broken
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr  6 23:20:02 PDT 1998
>Closed-Date:    Wed Jun 13 19:47:50 PDT 2001
>Last-Modified:  Wed Jun 13 19:52:59 PDT 2001
>Originator:     Kevin Day
>Release:        FreeBSD 2.2.5-STABLE i386
>Organization:
DragonData Internet Services
>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:
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mikeh 
State-Changed-When: Wed Jun 13 19:47:50 PDT 2001 
State-Changed-Why:  
Many changes have been made since then. If this is still a problem, 
please file another PR. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6234 
>Unformatted:
Kevin Day
