Date: Sat, 6 Mar 1999 16:58:59 -0600 (CST) From: Kevin Day <toasty@home.dragondata.com> To: wpaul@FreeBSD.ORG Cc: toasty@dragondata.com, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/6234 Message-ID: <199903062259.QAA13812@home.dragondata.com> In-Reply-To: <19990306194540.5475115318@hub.freebsd.org> from "wpaul@FreeBSD.ORG" at "Mar 6, 1999 11:45:40 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Synopsis: ypserv -d is broken > > State-Changed-From-To: open-closed > State-Changed-By: wpaul > State-Changed-When: Sat Mar 6 11:41:17 PST 1999 > State-Changed-Why: > > This PR basically says "it doesn't work" and fails to provide enough > details to diagnose the problem or reproduce it. The debug mode of > ypserv does indeed work; I've used it plenty of times and so have > others. I don't doubt that ypserv -d failed for this person for some > reason, however it was undoubtedly due to some other factor which > is impossible to trace without more information or experimentation > by the user. > > Also, the PR is for FreeBSD 2.2.5, which is quite old. > > -Bill > To follow up, this still happens in 3.1-RELEASE. Specificing 'ypserv -d' makes ypserv completely unresponsive, and never outputs any debugging... What more info do you want? :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903062259.QAA13812>