Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

domainname(1)

ypfiles(4)



admnis(1M)                        ONC R4.11                       admnis(1M)


NAME
       admnis - manage the NIS configuration

SYNOPSIS
       admnis -o set variable=value ...

       admnis -o get [ -qv ] [ variable ...  ]

       admnis -o start [ variable=value ...  ]

       admnis -o stop [ -qv ]

DESCRIPTION
       The admnis command manages the Network Information Service (NIS,
       formerly Yellow Pages) configuration for the system. NIS services are
       started automatically during system boot if the value of the system's
       NIS domain is not empty.

       A system may operate in one of three NIS roles:

       master    The NIS master maintains the original copies of all NIS
                 maps.  All updates to the maps must be done by the master.
                 The master pushes changed maps to its NIS servers.  The
                 master also responds to lookup requests from clients.

       server    The NIS servers maintain copies of the master's maps and
                 respond to lookup requests from clients.  Each subnet
                 should have at least two NIS servers.

       client    NIS clients look up naming information from NIS masters or
                 servers.

       The following variables are valid for the set and start operations:

       domain    The NIS domain name, as specified through domainname(1).

       role      The NIS role this system should assume.  This must be one
                 of master, server, client, or none.

   Operations
       set       Set the values of one or more NIS configuration variables
                 in the NIS configuration file.  This affects how NIS will
                 start during the next system boot, but does not affect the
                 current NIS state.

       get       Retrieve the values of one or more NIS configuration
                 variables from the NIS configuration file.

       start     Initiate NIS services, using the configuration variables
                 from /etc/nfs.params or the values supplied on the command
                 line.  If command line options are supplied, admnis updates
                 /etc/nfs.params to reflect those values.  Transitions from
                 any NIS role to any other NIS role are allowed.

                 If the role is master, admnis ensures that the maps in
                 /etc/yp/domain-name reflect the fact that this system is
                 the master for those maps.

       stop      Terminate NIS services.

   Options
       -q        For the get operation, display the output in

                     variable="value"

                 form.  For the stop operation, disable confirmations.

       -v        For the get operation, display the output in table form.
                 For the stop operation, confirm before stopping NIS
                 services.  This option is enabled by default.

FILES
       /etc/nfs.params
                 The database describing the NIS configuration.

DIAGNOSTICS
   Warnings
        -  The /etc/yp/domain directory does not exist.  The system reverts
           to acting as an NIS client.

   Errors
        -  The /dev/loop device does not exist or is not alive.

        -  The domain name is not set.

   Exit Codes
        0     The operation was successful.

        1     The operation was unsuccessful.

        2     The operation failed due to access restrictions.

        3     There was an error in the command line.

SEE ALSO
       domainname(1), ypfiles(4).

NOTES
       You must have write permission to the /etc/nfs.params file to use the
       set operation.  Only a user with appropriate privilege has such
       permission.

       On a generic DG/UX system, appropriate privilege is granted by having
       an effective UID of 0 (root). See the appropriate_privilege(5) man
       page for more information.

       On a system with DG/UX information security, appropriate privilege is
       granted by having one or more specific capabilities enabled in the
       effective capability set of the user.  See cap_defaults(5) for the
       default capabilities for this command.


Licensed material--property of copyright holder(s)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026