9.1. Existing NIS servers
If you have existing NIS (Network Information Service) servers serving user authentication information. Aptus
requires itself to be a master NIS server to serve netgroup and host name information. This doesn't mean Aptus cannot integrate with
existing NIS servers. Aptus server itself is both NIS client and NIS server, in fact Aptus server can be configured to only listen to itself
and serving itself. Your clients can be configured to use a different NIS domain and listen to your existing NIS servers. This will
separate just your Aptus server itself out of your existing NIS domain, leaving all your Aptus clients integrate with your existing NIS
managed network. So Aptus can still seamlessly integrate into your existing NIS managed network.
9.1.1. Disabling NIS on Aptus server
You can change the NIS settings in Aptus Configurator to use a separate
NIS server. Select No for use NIS at the module configuration.
Then you have to make sure you have disabled the NIS service (ypserv)
at the Aptus server by doing the following
$ /etc/rc.d/init.d/ypserv stop
Stopping YP server services: [OK]
$ chkconfig --level 345 ypserv off
$
|
This will disable the
ypserv on startup and turn off NIS .
9.1.2. Use existing NIS servers
You can go to Aptus Configurator -> Group configuration
-> NIS Client and specify your desired NIS server address and domain name.
You may also change this by hand in the groupfs located in
/var/opt/aptus/mygroup/groupfs/etc/yp.conf . See man 5 yp.conf for
more details of the file format.
