I may be misunderstanding what you are saying here, but master.passwd
on the slave servers should never get updated with NIS information.
That line that goes at the end tells the authentication process to
look to NIS for further information...same goes with the line that
goes in the group
Be hot on typo.
My case :
% sudo tail -1 /etc/ma*d
+:
% sudo tail -1 /etc/ma*d|wc -c
11
%
Sorry, this was a typo in my email, not the master.passwd. There are
9 colons in the actual file.
(Again apologies if you get this multiple times .. it's late and I did
not notice
Interesting...something that pops into my mind is something obvious
since it was stated in the handbook, but needs to be said
anyway...when you add stuff to the master.passwd file, do you re-make
the database? Also, if you follow the directions in the handbook,
they suggest you make a different
Interesting...something that pops into my mind is something obvious
since it was stated in the handbook, but needs to be said
anyway...when you add stuff to the master.passwd file, do you re-make
the database? Also, if you follow the directions in the handbook,
they suggest you make a
Interesting...something that pops into my mind is something obvious
since it was stated in the handbook, but needs to be said
anyway...when you add stuff to the master.passwd file, do you re-make
the database? Also, if you follow the directions in the handbook,
they suggest you make a
On Sun, 10 Oct 2004 12:55:06 -1000
William Bierman [EMAIL PROTECTED] wrote:
Hello. I have searched the archives for this, to no avail.
I am attempting to setup an NIS domain. I have followed the steps in
the handbook, and have succesfully setup my master and clients (I have
no slave
I may be misunderstanding what you are saying here, but master.passwd
on the slave servers should never get updated with NIS information.
That line that goes at the end tells the authentication process to
look to NIS for further information...same goes with the line that
goes in the group file.
