Date: Mon, 28 Jun 1999 14:58:15 -0700 (PDT) From: Doug <Doug@gorean.org> To: Mitch Collinsworth <mkc@Graphics.Cornell.EDU> Cc: Doug White <dwhite@resnet.uoregon.edu>, freebsd-questions@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: 3.2-R: problem with inetd and NIS Message-ID: <Pine.BSF.4.05.9906281457480.7668-100000@dt054n86.san.rr.com> In-Reply-To: <199906221954.AA279571283@broccoli.graphics.cornell.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Jun 1999, Mitch Collinsworth wrote:
> >Did you shutdown inetd totally then restart it? Apparently kill -HUP
> >inetd doesn't quite work correctly for certain configuration files.
>
> No I didn't. I've never heard of such a thing. However... It does
> in fact work! Now that we know this, it is conceivable 3.0-R and 3.1-R
> may have the same problem since I can't say for sure that I didn't
> reboot those systems sometime between configuration and testing.
>
> I would have to classify this as a bug. The HUP signal should cause
> all configuration info to be re-loaded.
It is a bug, and it's fixed in -stable.
HTH,
Doug
--
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
-- Will Rogers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906281457480.7668-100000>