Date: Mon, 7 Jun 1999 13:25:07 +0200 From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: John Baldwin <jobaldwi@vt.edu> Cc: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>, Mike Nowlin <mike@argos.org>, Wes Peters <wes@softweyr.com>, freebsd-security@FreeBSD.ORG, Dag-Erling Smorgrav <des@flood.ping.uio.no>, John Baldwin <jobaldwi@smtp1.erols.com> Subject: Re: NIS strangeness Message-ID: <19990607132507.A69066@internal> In-Reply-To: <199906071038.GAA16710@smtp1.erols.com>; from John Baldwin on Mon, Jun 07, 1999 at 06:38:13AM -0400 References: <19990607083131.A43845@internal> <199906071038.GAA16710@smtp1.erols.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 07-Jun-1999 at 06:38:13 -0400, John Baldwin wrote: > > On 07-Jun-99 Andre Albsmeier wrote: > > On Sun, 06-Jun-1999 at 22:27:52 -0400, John Baldwin wrote: > >> > >> On 06-Jun-99 Dag-Erling Smorgrav wrote: > >> > Mike Nowlin <mike@argos.org> writes: > >> >> > Did you add the +::::::: entry to the passwd file? > >> >> > Be sure to do group as well, if that's the problem. ;^) > >> >> Used "vipw" to add it into /etc/master.passwd, and /etc/passwd now hsa > >> >> +:*::::: in it..... Seems OK there..... :) > >> > > >> > Remove the star - that's what's preventing kathleen from logging in. > > > > Now, please let me jump in here... I am currently debugging some curious > > effects of NIS/ELF together with John Polstra. I am looking for > > someone who has: > > > > 1.) A recent 3.2-STABLE installation with at least a > > version 1.13.2.8 of libexec/rtld-elf/rtld.c > > > > 2.) A working NIS master server with the machine from 1.) > > > > 3.) Two or more slave server with the machine from 1.) > > > > > > If all the above points apply, I would like to know the output of > > the following command on the NIS master (replace the hostnames, they > > are not important here): > > > > yppush -vvv <any NIS map, e.g. mail.aliases> > > Well, the server is running 2.2.7. We've had problems using 3.0 and 3.1 > machines as slaves, so our only slave right now is running Digital UNIX. The > next chance I get, I'll setup a slave server on one of our 3.2 servers and see > how that goes. There are plans to upgrade the NIS master to 3.2 eventually, > just not quite yet. :( I see. The problem occures when the master runs a libexec/rtld-elf/rtld.c with version 1.13.2.8 or newer and has to update 2 or more slaves. Both slaves get updated but the callback to the master, indicating that all is well, fails for the second slave. So, if anyone got the setting as I described in the previous mail, please run the above yppush command and send me the output. Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990607132507.A69066>