You can find the vasyp.pkg file in the client directory for your Solaris operating system on the installation media.
To install and configure vasyp on Solaris
# /etc/init.d/rpc stop
To ensure that the system ypserv daemon does not start at boot time, make sure that the following directory does not exist:
/var/yp/$domainname
where $domainname matches the NIS domain returned by domainname.
|
Note: You do not need to do this if the machine is not configured as a NIS server. |
# /usr/lib/netsvc/yp/ypstop
# svcadm disable vasypd
# svcadm disable network/nis/server
|
Note: When installing the Authentication Services vasypd Unix component on Solaris 10 (or greater), you must have the rpcbind service enabled on the host for this service to start. To enable it, run this command: # /usr/sbin/svcadm enable -s network/rpc/bind |
# pkgadd -d vasyp_SunOS_<platform>-<version>.pkg all
localhost
# domainname example.com
where example.com is the domain to which your machine has been joined.
|
Note: This only sets your NIS domain name for the current environment. |
example.com
where example.com is the Active Directory domain to which you are joined.
# /etc/init.d/vasypd start
# /etc/init.d/rpc start
# /usr/lib/netsvc/yp/ypstart
You can now use the NIS utilities like ypwhich and ypcat to query vasyp for NIS map data.
|
Note: For Solaris 10 (or greater), ypbind may not bind to vasyp until some actual NIS requests occur which can take up to 30 seconds. |
|
Note: For Solaris 10 (or greater), you must restart ypbind by entering the following command. # svcadm restart network/nis/client |
You can find the vasyp.depot file in the client directory for your HPUX operating system on the installation media.
To install and configure vasyp on HP-UX
# /sbin/init.d/nis.server stop # /sbin/init.d/nis.client stop
To ensure that the system ypserv daemon does not start at boot time, modify /etc/rc.config.d/namesvrs and set the NIS_MASTER_SERVER and NIS_SLAVE_SERVER variables to 0.
|
Note: You do not need to do this if the machine is not configured as a NIS server. |
# swinstall -s /cdrom/hpux-<platform>/vasyp_<platform>-<version>.depot vasyp
localhost
# domainname example.com
where example.com is the domain to which your machine has been joined.
# /sbin/init.d/vasypd start
# /sbin/init.d/nis.client start
You can now use the NIS utilities like ypwhich and ypcat to query vasyp for NIS map data.
You can find the vasyp.bff file in the client directory for your AIX operating system on the installation media.
To install and configure vasyp on AIX
# stopsrc -s ypbind # stopsrc -s ypserv
Also ensure that all entries dealing with ypserv and ypbind in /etc/rc.nfs are commented out.
|
Note: You do not need to do this if the machine is not configured as a NIS server. |
# installp -ac -d vasyp_AIX_<platform>.<version>.bff all
127.0.0.1
# /etc/rc.d/init.d/vasypd start
|
Note: Do not configure the NIS client using the standard AIX configuration instructions. Normally, you configure the system domain name and enable the NIS client in /etc/rc.nfs. For vasyp to work correctly on AIX, you must disable any NIS configuration in the /etc/rc.nfs file. |
You can now use the NIS utilities like ypwhich and ypcat to query vasyp for NIS map data.
By default, the vasyp daemon only searches the Active Directory container, or organizational unit (OU) in which the Unix computer object was created. You can override this search location by configuring the search-base option in vas.conf. This allows you to have different sets of NIS maps for different groups of Unix hosts.
For more information on the search-base option, refer to the vasypd section of the vas.conf man page.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy