From owner-freebsd-questions Mon Jun 28 14:58:22 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 0C8A314CBB; Mon, 28 Jun 1999 14:58:19 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA07754; Mon, 28 Jun 1999 14:58:15 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 28 Jun 1999 14:58:15 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Mitch Collinsworth Cc: Doug White , freebsd-questions@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: 3.2-R: problem with inetd and NIS In-Reply-To: <199906221954.AA279571283@broccoli.graphics.cornell.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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