Nobody: Difference between revisions

From DISI
Jump to navigation Jump to search
(Created page with "If you are on a server that is listing the owner of a file as nobody:nobody that is the result of a missing line in a config file. It's a very simple fix though: edit the fil...")
 
No edit summary
 
Line 8: Line 8:
This is the result of user/group IDs not knowing how to map themselves correctly over NFS. The idmapd file helps adjust those mappings.
This is the result of user/group IDs not knowing how to map themselves correctly over NFS. The idmapd file helps adjust those mappings.


[[Category:Internal]]
[[Category:Sysadmin]]

Latest revision as of 07:08, 13 March 2014

If you are on a server that is listing the owner of a file as nobody:nobody that is the result of a missing line in a config file. It's a very simple fix though:

edit the file: /etc/idmapd.conf and add the line

DOMAIN=bkslab.org

Then service nslcd restart (or service sssd restart), whichever is in use. You *may* need to remount the nfs mounts (umount /srv/nfs/*)

This is the result of user/group IDs not knowing how to map themselves correctly over NFS. The idmapd file helps adjust those mappings.