Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ ypinit(1M) — DG/UX R4.11MU05

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

makedbm(1M)

ypmake(1M)

yppush(1M)

ypserv(1M)

ypxfr(1M)

ypfiles(4)



ypinit(1M)                     DG/UX R4.11MU04                    ypinit(1M)


NAME
       ypinit - build and install Network Information Service database

SYNOPSIS
       /usr/etc/yp/ypinit -m

       /usr/etc/yp/ypinit -s mastername

DESCRIPTION
       ypinit sets up a Network Information Service database on an NIS
       server.  It can be used to set up a master or a slave server.  You
       must have appropriate privilege to run it.  It asks a few, self-
       explanatory questions, and reports success or failure to the
       terminal.

       It sets up a master server using the simple model in which that
       server is master to all maps in the data base.  This is the way to
       bootstrap the NIS system; later if you want you can change the
       association of maps to masters.  All databases are built from
       scratch, either from information available to the program at runtime,
       or from the ASCII data base files in /etc.  Some of these files are
       listed below under FILES.  All such files should be in their
       ``traditional'' form, rather than the abbreviated form used on client
       machines.

       An NIS database on a slave server is set up by copying an existing
       database from a running server.  The mastername argument should be
       the hostname of NIS server (either the master server for all the
       maps, or a server on which the data base is up-to-date and stable).

       Read ypfiles(4) and ypserv(1M) for an overview of the Network
       Information Service.

OPTIONS
       -m     Indicate that the local host is to be the NIS master.

       -s     Set up a slave database.

FILES
       /etc/passwd
       /etc/group
       /etc/hosts
       /etc/networks
       /etc/services
       /etc/protocols
       /etc/ethers

SEE ALSO
       makedbm(1M), ypmake(1M), yppush(1M), ypserv(1M), ypxfr(1M),
       ypfiles(4), appropriateprivilege(5).
       capdefaults(5).

NOTE
       For systems supporting the DG/UX Capability Option, appropriate
       privilege is defined as having one or more specific capabilities
       enabled in the effective capability set of the user.  See
       capdefaults(5) for the default capabilities for this command.

       On systems without the DG/UX Capability Option, appropriate privilege
       means that your process has an effective UID of root. See the
       appropriateprivilege(5) man page for more information.



Licensed material--property of copyright holder(s)

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