This is a legacy process, and should be replaced with a different process, using LDAP or something, in new installations. However, if you are working in a legacy environment, this should do the trick for relatively sane installations of NIS and new Ubuntu installations.<\/p>\n
The NIS\u00a0domainname\u00a0is\u00a0nisDomain<\/b>. Please note that in the context of NIS databases, “domainname” is an arbitrary string (you just pick one) and has nothing to do with your canonical domain name in DNS. [in other words, replace\u00a0nisDomain<\/strong> with your local NIS domain].<\/p>\n Server Configuration<\/b><\/p>\n Remember, please, to copy the database files before you edit them so that if you bork up royally, you can just go back easily. Use git, use cp, who cares, just make sure you have a known sane version to go back to quickly.<\/p>\n In order to add the client to the NIS database you, need to log into\u00a0nisServer<\/b>\u00a0and edit the following files:<\/p>\n In\u00a0ethers<\/b>, you need to add the MAC (Ethernet) address. Get this information from the client machine by running\u00a0ifconfig<\/b>. Once that is done you need to:<\/p>\n in order to rebuild the NIS database. Client Configuration<\/b><\/p>\n If you’re going to do this to more than one machine, configure it then clone it. Get it right once and use copies somehow, with whatever technology you usually use.<\/p>\n This article assumes that client machines should run an up-to-date installation of Ubuntu 16.04 LTS (Xenial Xerus). Please consider\u00a0unattended-upgrades<\/b>. Also, conventional wisdom states that you should have at least one local user on the machine.<\/p>\n Add\u00a0nisServer<\/b>\u00a0to \/etc\/hosts, just for sanity: Install the programs the client machine needs: Explicitly set rpcbind as allowed over network: Tell the client that NIS databases are available, and to query them first for the following categories by editing nsswitch. Note that there order of placement here matters; we have had anomalous permissions behavior if\u00a0files<\/b>\u00a0precedes\u00a0nis<\/b>\u00a0in some cases. Ensure\u00a0portmap starts on boot by adding\u00a0service\u00a0portmap start\u00a0<\/b>to \/etc\/rc.local: You need to run\u00a0update-rc.d nis defaults\u00a0<\/b>to install\u00a0nis\u00a0<\/b>services at\u00a0boot time, however, note that the default script links the boot script as\u00a0S01nis<\/b>\u00a0in\u00a0\/etc\/rc5.d<\/b>, so if you find that nis is failing after boot, defaults may not be sufficient and you can try again with a higher S number.<\/p>\n You could put your NFS shares in \/etc\/fstab<\/strong>. Or you could\u00a0sudo apt install autofs<\/b> File:\u00a0\/etc\/auto.home<\/b><\/p>\n Note that +auto.home<\/strong> is a pointer reference to the\u00a0\/etc\/yp\/auto.home<\/b> (or something similar)\u00a0file on\u00a0your nisServer.<\/b><\/p>\n Lastly, we have to configure\u00a0lightdm<\/b>, Ubuntu’s graphical login client. First, you have to enable manual logins via username. Second, there’s an is apparently an issue with some default sessions for some users, for some reason; at times, if the default session isn’t explicitly set, it borks. Anyway, it’s an easy fix. Create a local configuration by creating a conf file in the appropriate directory. Call it nis.conf<\/strong> or so. Basically lightdm will load\u00a0*.conf<\/b>\u00a0in this dir when it runs, so you can call it anything. (This is debian convention.) This file has no man page, but googling around and trying variants helped. There’s a sample of the file (with syntax) at\u00a0\/usr\/share\/doc\/lightdm\/lightdm.conf.gz. Anyway, create this: At this point, the client’s configuration is done.<\/i> The client knows the server is there, and the server knows the client exists, so you should be able to log in with your nisServer<\/strong>\u00a0credentials.<\/p>\n You need to\u00a0sudo reboot<\/b>\u00a0to restart the client machine, ensure it brings the services up properly on every reboot, and log in to test it, preferably with more than one user.<\/p>\n","protected":false},"excerpt":{"rendered":" This is a legacy process, and should be replaced with a different process, using LDAP or something, in new installations. However, if you are working in a legacy environment, this should do the trick for relatively sane installations of NIS and new Ubuntu installations. The NIS\u00a0domainname\u00a0is\u00a0nisDomain. Please note that in the context of NIS databases, […]<\/p>\n","protected":false},"author":3412,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wds_primary_category":0},"categories":[5,19,18,16],"tags":[],"_links":{"self":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/posts\/114"}],"collection":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/users\/3412"}],"replies":[{"embeddable":true,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/comments?post=114"}],"version-history":[{"count":5,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/posts\/114\/revisions"}],"predecessor-version":[{"id":134,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/posts\/114\/revisions\/134"}],"wp:attachment":[{"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/media?parent=114"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/categories?post=114"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fs.wp.odu.edu\/sobrien\/wp-json\/wp\/v2\/tags?post=114"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\nIn\u00a0netgroup<\/b>, you need to add the client machine’s name.
\nIn\u00a0hosts<\/b>, you need to add the IPv4 address and its name. Note that the IP address is assigned automatically via DHCP, and they are fairly static, but could change at any time.<\/p>\ncd \/var\/yp<\/b>
\nsudo make<\/b><\/code><\/p>\n
\nYou shouldn’t need to do a\u00a0service nis restart<\/b>. You shouldn’t need to do a\u00a0service ypbind restart<\/b>.<\/p>\n
\nFile:\u00a0\/etc\/hosts<\/b><\/p>\n127.0.0.1 localhost
\n192.168.1.X clientName
\n192.168.1.Y nisServer<\/code><\/p>\n
\nsudo apt install nis rpcbind nfs-common<\/b>.
\nUpon installation you will be asked the NIS domainname, here\u00a0nisDomain.<\/b>
\nAdd nisServers’s IP to \/etc\/yp.conf:
\nFile: \/etc\/yp.conf<\/b><\/p>\nypserver 192.168.1.Y<\/code><\/p>\n
\nFile:\u00a0\/etc\/hosts.allow<\/b><\/p>\nrpcbind: \u00a0 \u00a0 \u00a0 127.0.0.1
\nrpcbind: \u00a0 \u00a0 \u00a0 192.168.1.Y<\/code><\/p>\n
\nFile:\u00a0\/etc\/nsswitch.conf<\/b><\/p>\npasswd: \u00a0 \u00a0 \u00a0 \u00a0 nis files
\ngroup: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0nis files
\nshadow: \u00a0 \u00a0 \u00a0 \u00a0 nis files
\nhosts: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0nis files mdns4_minimal [NOTFOUND=return] dns
\nnetworks: \u00a0 \u00a0 \u00a0 nis files
\nprotocols: \u00a0 \u00a0 \u00a0db files nis
\nservices: \u00a0 \u00a0 \u00a0 db files nis
\nethers: \u00a0 \u00a0 \u00a0 \u00a0 db files nis
\nrpc: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0db files nis
\nnetgroup: \u00a0 \u00a0 \u00a0 nis
\npublickey: \u00a0 \u00a0 \u00a0nis
\nautomount: \u00a0 \u00a0 \u00a0nis
\naliases: \u00a0 \u00a0 \u00a0 \u00a0nis<\/code><\/p>\n
\nFile:\u00a0\/etc\/rc.local<\/b><\/p>\n#!\/bin\/sh -e
\n#
\n# rc.local
\n#
\n# This script is executed at the end of each multiuser runlevel.
\n# Make sure that the script will \"exit 0\" on success or any other
\n# value on error.
\n#
\n# In order to enable or disable this script just change the execution
\n# bits.
\n#
\n# By default this script does nothing.
\nservice portmap start
\nexit 0<\/code><\/p>\n
\nAutofs is the file system service that mounts the user’s home directory via NFS when the directory is needed, including at login. In order to configure it, you need to edit the following files:
\nFile:\u00a0\/etc\/auto.master<\/b><\/p>\n# This is a 'master' automounter map and it has the following format:
\n# mount-point [map-type[,format]:]map [options]
\n# For details of the format look at auto.master(5).
\n#
\n\/misc \u00a0 \/etc\/auto.misc
\n\/home \u00a0 \/etc\/auto.home
\n#
\n# NOTE: mounts done from a hosts map will be mounted with the
\n# \u00a0 \u00a0 \u00a0 \"nosuid\" and \"nodev\" options unless the \"suid\" and \"dev\"
\n# \u00a0 \u00a0 \u00a0 options are explicitly given.
\n#
\n#\/net \u00a0 -hosts
\n\/net \u00a0 yp \u00a0 \u00a0 auto.net<\/a>
\n#
\n# Include \/etc\/auto.master.d\/*.autofs
\n# The included files must conform to the format of this file.
\n#
\n+dir:\/etc\/auto.master.d
\n#
\n# Include central master map if it can be found using
\n# nsswitch sources.
\n#
\n# Note that if there are entries for \/net or \/misc (as
\n# above) in the included master map any keys that are the
\n# same will not be seen as the first read key seen takes
\n# precedence.
\n#
\n+auto.master<\/code><\/p>\n# This is the trad way
\n* \u00a0 \u00a0 nisServer:\/home\/&
\n#
\n# This is a way to do it by pulling a file from your nis directory on server
\n+auto.home<\/code><\/p>\n
\nFile:\u00a0\/etc\/lightdm\/lightdm.conf.d\/nis.conf<\/b><\/p>\n[SeatDefaults]
\ngreeter-show-manual-login=true
\nuser-session=true<\/code><\/p>\n