Skip to main content

NIS and GIDs less than 100

$#%@&%#@$!!!
I was having an issue with existing local user accounts on my NIS test server. As indicated in /etc/nssswitch.conf, local files override NIS settings. So starting with a clean system - as far as user accounts go - is a great idea.
However, I was also using the local system group wheel for daily management purposes. So it goes without saying that I was confused as to why my own account did not get wheel permissions on my test server. Doing an "id myuserid" on the NIS server showed uid=500(myuserid) gid=100(users) groups=10(wheel),100(users), while the same command on my NIS test server showed uid=500(myuserid) gid=100(users) groups=100(users). What gives?
Well, there is a file called /var/yp/Makefile that lists which UIDs and GIDs will be transmitted i.e. synced over NIS. Default is 500. So any user account and group below that will not get replicated. *sigh* I did read that while installing but forget when testing. An old Pipermail archive pointed the way...

I now have a local group called 'sysop' with gid 600 (groupadd -g 600 sysop) for all management purposes and uids start at 500 anyway. Case closed.
Labels:

Comments

Post a Comment

Popular posts from this blog

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries 20 seconds time to live for negative entries 66254 cache hi...
2 comments
Read more

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.
1 comment
Read more

Logbook and Note Book

I'm no longer actively working with Linux although I use it privately. This was my work logbook during my job as a Linux Engineer and Architect for KPN Data Centers.  I'm keeping this as a log and note book. Who knows when it comes in handy although much will be outdated. If you find any good resources or more current howtos for what was written here, let me know!
Post a Comment
Read more