SETUP_CLIENT(8)

NAME
setup_client - create or remove an NFS client

SYNOPSIS
/usr/etc/install/script/setup_client
op clientname yp_type swapsize
rootpath swappath
homepath execpath kvmpath arch

DESCRIPTION

setup_client adds an NFS client to a server, or removes one. It can only be run by the super-user. It is also used by suninstall(8).

The op argument indicates which operation to perform; it can be either add or remove, to indicate whether to add or remove a client. clientname is the hostname of the client. yp_type indicates the type of YP server or service to provide to the client, if any; it can be one of master, slave, client or none. swapsize is the number of bytes reserved for client's swap file. rootpath is the pathname of parent directory in which various client root directories reside; rootpath/clientname is the pathname of the client's root directory. swappath is the pathname of parent directory in which various client swap files reside; swappath/clientname is the pathname of the client's swap file. homepath is the pathname of the (parent) directory in which the various home directories are to reside; it is the pathname of the directory that the client is to mount as /home. execpath is the full pathname of the directory in which the executables for the architecture specified by the arch argument. This is the directory that the client mounts as /usr. arch specifies the client's architecture (for instance, sun4, sun3...). setup_client with no arguments displays a usage message that includes the proper arch argument for each supported architecture.

USAGE

Before you add or remove a client, you must first make sure that the Internet and Ethernet addresses for clientname are listed in the YP hosts database (if the server is running the YP name service), or in the server's /etc/hosts and /etc/ethers databases, respectively (otherwise). Then, run setup_client with the add or remove operation. When adding a client, you must then bootstrap that client machine.

You cannot add a client to a server that does not support the specified architecture. The executable directory for that client's architecture must be present on the server. If this file is absent, an error results.

setup_client updates the /etc/bootparams file. If the server is a YP master, it updates local YP database. It does not propagate the local update to other YP servers. To propagate the updates, use the following commands:
    example# cd /var/yp
    example# make

If the server is running the YP name service but is not a YP master, setup_client issues a warning to indicate that the database is out of date.

When arch is given as sun2, suninstall issues a reminder to run the /usr/etc/ndbootd daemon for booting Sun-2 systems.

setup_client creates swappath/clientname with the size, (number of bytes) you specify. You can append one of K or k to indicate kilobytes, M or m to indicate megabytes, or B or b to indicate 512-byte blocks, to size. Otherwise, size is taken to indicate an exact byte count.

suninstall updates the /etc/exports file to allow root access to each client's root file system. It exports the client's swap and dump partitions only to the client. Note: the system administrator should verify that the /etc/exports file contains correct information, and that file systems are exported to the correct users and groups. Refer to exportfs(8) for details on exporting file systems.

EXAMPLES
This example shows how to add a Sun-4 system NFS client to a server.

    example# setup_client add frodo client 16M /exports/roots /exports/swaps /exports/dumps /home \
    /exports/execs/sun4/4.0 sun4

To remove this client, you would merely substitute remove for add in the above example.

FILES
/etc/hosts
/etc/ethers
/usr/etc/ndbootd
/etc/bootparams
/etc/exports

SEE ALSO
exportfs(8), setup_exec(8) suninstall(8)

DIAGNOSTICS

incorrect number of arguments
    Check number and order of the arguments.

must be run as root (super-user).
    You must be root to use setup_client.

invalid operation type ``xx''.
    Valid operations are add and remove.

ATTENTION: xxxxxxxx -> boot.sun? not created.
    (Sun-3 systems only.) A symbolic link can not be created because the boot file does not exist.

ATTENTION: xxxxxxxx.SUN? -> boot.sun? not created.
    (Other than Sun-3 systems.) A symbolic link can not be created because the boot file does not exist.
ATTENTION: /usr/etc/ndbootd needs to be running on server before bringing up ``client''.
    The Sun-2 system boot daemon must be running in order to bootstrap a Sun-2 system.