Bug 5268 - NIS disables(?) local accounts
NIS disables(?) local accounts
Product: Red Hat Linux
Classification: Retired
Component: passwd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-09-21 10:36 EDT by aram
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-10-05 02:13:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description aram 1999-09-21 10:36:40 EDT
I have 2 redhat 6.0 boxes running NIS and having local
accounts. Local accounts except root (2 login-able accounts)
don't work anymore, i.e. I can't login using their
username/passwd combination via (virtual) console or
remotely. I can log in as root from console or login as an
NIS user. I can edit /etc/passwd and add new local users
that way, create/chown their dirs, but when I `passwd
newuser` as root I type in the passwd twice and get the
result that all auth token have been updated successfully,
while /etc/passwd still shows an unchanged passwd field. No
shadow passwds.

I can `/bin/su localuser` from root and stuff works, but
that is less than ideal.

/etc/nsswitch tells it to looks at (local) files before nis.
The only pointer I have is the /var/log/messages line that
says that the pwdb structure is no longer valid. And when I
try to `passwd` from a local user account (into which I've
su'ed from root) I get "Auth service cannot retrieve auth
Comment 1 Cristian Gafton 1999-10-05 02:13:59 EDT
Are you sure this is not a problem of having shared UIDs between NIS
and the local system?

Also, you might not want to edit the local /etc/passwd by hand - use
useradd instead. There is a bug in passwd that will refuse to set the
passwords for accounts with an empty password field.

Note You need to log in before you can comment on or make changes to this bug.