From owner-freebsd-questions Tue Jun 22 11:55:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 80B4715687; Tue, 22 Jun 1999 11:55:10 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id LAA33412; Tue, 22 Jun 1999 11:55:08 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 22 Jun 1999 11:55:07 -0700 (PDT) From: Doug White To: Mitch Collinsworth Cc: freebsd-questions@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: 3.2-R: problem with inetd and NIS In-Reply-To: <199906212206.AA264992771@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 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. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message