Subject: bin/14665: Sporadic NIS failure with 1.5.3_ALPHA, 1.5.2, -current
To: None <email@example.com>
From: Mason Loring Bliss <firstname.lastname@example.org>
Date: 11/21/2001 13:12:14
>Synopsis: Sporadic NIS failure with 1.5.3_ALPHA, 1.5.2, -current
>Arrival-Date: Wed Nov 21 10:13:00 PST 2001
>Originator: Mason Loring Bliss
>Release: NetBSD 1.5.3_ALPHA
M a s o n L o r i n g B l i s s email@example.com
awake ? sleep : random() & 2 ? dream : sleep; https://acheron.ne.mediaone.net/
System: NetBSD acheron.in.hades 1.5.3_ALPHA NetBSD 1.5.3_ALPHA (MLB) #6: Fri Nov 16 17:55:25 EST 2001 firstname.lastname@example.org:/usr/src-1-5/sys/arch/i386/compile/MLB i386
NIS is having trouble with some (but not all) accounts, whereby using rlogin,
for example, fails to successfully authenticate at first, requiring the user
to enter a password regardless of the presence of a correct entry in .rhosts.
Here's the relevant excerpt from a destination system:
Nov 21 12:47:38 targetsystem inetd: connection from originatingsystem, service login (tcp)
Nov 21 12:47:38 targetsystem rlogind: someuser@originatingsystem as someuser: iruserok failed
The NIS server in all cases is 1.5.3_ALPHA, and destination systems have been
1.5.2, -current, and 1.5.3_ALPHA systems.
Note that while rlogin seems to fall back on a password exchange with
the user which then works, things like "rsh target foo" will just fail
out of hand every time for non-working accounts. Also note that what
distinguishes working accounts from non-working accounts is not yet
known. Being logged in to the destination box already seems not to make
Note that "ypcat passwd" returns everything it should consistently.
No idea what's wrong, yet.