Sorry for the late summary on this but here is what fixed the problem.
Thanks to all of you that did reply. I have listed the replies below.
I hope I haven't left anyone out.
The reason this took so long is that nothing seemed to be helping the
problem. Today as a last ditch effort I tried putting a + sign in the local
passwd file on this machine and then I could login as a user over the LAN
and then su to root once on the machine. This is how all other machines
are set up on our LAN, nis for all users and root controlled locally on
each machine. Now I have taken the plus back out of the passwd file and
and set the nsswitch the same as all other machines and its still
working!?
Thanks again to everyone and to Joe Buhr since after reviewing his mail
I decided to try the + sign. I still don't understand why that fixed the
problem.
Regards
Howard
Timothy Lindgren [tlindgre@enron.com] wrote:
passwd: nis [NOTFOUND=continue] files
And obviously dont have root in a nis table.
David Evans [DJEVANS@au.oracle.com] wrote:
You probably want "compat" for passwd but you may find
files [NOTFOUND=continue] nis
more suitable depending on you usage. If you are using +/- syntax
you can only go with compat.
Buhr Joseph-C17297 [Joe.Buhr@motorola.com] wrote:
If memory servers me correctly (been away from nis for a while)...
I think you need the line to be
passwd: files nis
and at the bottom of your /etc/passwd file put a + sign.
Daniel.Polombo@detexis.thomson-csf.com wrote:
Isn't there a [NOTFOUND=Return] between 'nis' and 'files'?
It sounds just like you only have access to the first
option.
Simon Dray [Simon.Dray@bbsrc.ac.uk] wrote:
I would think that you are trying to su to root from a user not registered
in the nis database.
Adzman SK [adzman@no1.nc.com.my]wrote:
I think what might have happen here is that you populated root
(and several other system accounts) on the NIS server. So that's why when
/etc/nsswitch.conf has the entry "passwd: nis files", you cannot SU. It
is because you are supplying the wrong password.
Probably you should check your NIS server and remove all the
system accounts. System accounts need not be populated as the appear in
all the machine/servers/workstations.
Mike DeMarco [mikejd@bnpcn.com]wrote:
change it to passwd: files [NOTFOUND=continue] nis
Jonathan.Loh@bankofamerica.com wrote:
Do you by chance have root on nis+?
Bruce R. Zimmer [bzimmer@all-phase.com]wrote:
The problem is that you have a root user in your NIS database, and the
password for that machine and the NIS root user do not match. Easiest
solution would be to remove root from NIS and locally manage root on
each machine.
-----Original Message-----
From: Howard Boggs [mailto:hboggs@bridgept.com]
Sent: Tuesday, July 27, 1999 6:31 PM
To: sun-managers@sunmanagers.ececs.uc.edu
Cc: Howard Boggs
Subject: nsswitch.conf
This is a strange problem that one of you may
have seen before. I can not su to root on one
machine when the passwd section of nsswitch.conf
is set to "passwd: nis files" if I change it to
"passwd: files nis" then no user can log in but
I can su to root. Our user accounts are all nis.
Any help would be greatly appreciated.
TIA and as always will summarize.
Howard
--------------------------------------------
Howard Boggs - Information Officer
BridgePoint Technical Manufacturing
Phone: 512-637-4718
Fax: 512-637-4750
mobile: 512-658-0131
hboggs@bridgept.com
www.bridgept.com
--------------------------------------------
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:25 CDT