From owner-freebsd-questions Tue Jun 22 12:54:51 1999 Delivered-To: freebsd-questions@freebsd.org Received: from broccoli.graphics.cornell.edu (BROCCOLI.GRAPHICS.CORNELL.EDU [128.84.247.53]) by hub.freebsd.org (Postfix) with ESMTP id 9E1C41552E; Tue, 22 Jun 1999 12:54:47 -0700 (PDT) (envelope-from mkc@Graphics.Cornell.EDU) Received: from graphics.cornell.edu (localhost.graphics.cornell.edu) by broccoli.graphics.cornell.edu with ESMTP (1.37.109.16/16.2) id AA279571283; Tue, 22 Jun 1999 15:54:43 -0400 Message-Id: <199906221954.AA279571283@broccoli.graphics.cornell.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: Doug White Cc: freebsd-questions@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: 3.2-R: problem with inetd and NIS In-Reply-To: Your message of "Tue, 22 Jun 1999 11:55:07 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Jun 1999 15:54:42 -0400 From: Mitch Collinsworth Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Mon, 21 Jun 1999, Mitch Collinsworth wrote: > >> >> I'm not sure whether this is a bug or a feature. It doesn't seem to >> >> be in the release notes so perhaps that makes it a bug. :-) >> >> >> >> I am putting an entry in inetd.conf with a non-root user field. >> >> This user is defined in NIS rather than in /etc/master.passwd. >> >> On 3.0-R and 3.1-R this works. On 3.2-R when I HUP inetd I get: >> >> "No such user 'user', service ignored". Putting a non-NIS entry >> >> into master.passwd for this user does get inetd to start the >> >> service. >> > >> >This begs the question, is NIS working? How did you activate NIS? >> >> Yes, NIS is working for everything except inetd in 3.2-R. > >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. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message