NAME

setup_client − create or remove an NFS client

SYNOPSIS

/usr/etc/script/install/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:

add Add a client. 

remove
Remove a client.

clientname is the hostname of the client. 

yp_type indicates the type of Yellow Pages server or service to provide to the client, if any; it can be one of:

master

slave

client

none

swapsize is the number of bytes reserved for client’s swap file (for example, 16M, 16K, 32G). 

rootpath is the pathname of the parent directory in which various client root directories reside; setup_client creates a directory, rootpath/clientname, which is the pathname of the client’s root directory. 

swappath is the pathname of the parent directory on the server in which various client swap files reside; setup_client creates a directory, swappath/clientname, is the pathname of the client’s swap file. 

homepath is the pathname of the parent directory on the server 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 on the server in which the executables for the application architecture specified by the arch argument reside.  This is the directory that the client mounts as /usr. 

kvmpath is the full pathname of the directory on the server in which the kernel-specific executables for the architecture specified by the arch argument reside.  This is the directory that the client mounts as /usr/kvm. 

arch specifies the client’s kernel architecture (for instance, Sun4, Sun3x...). See the −k option of arch(1) for further explanation of “kernel architecture” and examples of valid kernel architectures.  setup_client with no arguments displays a usage message that includes the proper arch argument for each supported kernel 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 YP), or in the server’s /etc/hosts and /etc/ethers databases, respectively (if 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 directories for that client’s kernel and application architectures must be present on the server.  If these directories are absent, an error results.  See setup_exec(8) for information on setting up a machine to support clients of a different architecture. 

setup_client updates the /etc/bootparams file.  If the server is a YP master, it updates the 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 YP 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, setup_client issues a reminder to run the /usr/etc/ndbootd daemon for booting Sun-2 systems. 

setup_client creates swappath/clientname with the swapsize (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 swapsize. Otherwise, swapsize is taken to indicate an exact byte count. 

setup_client 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 NFS client called frodo with a 16 megabyte swap space to a server. 

example# setup_client  add  frodo  client  16M  /export/root  /export/swap  /home  \
/export/exec/sun4  /export/exec/kvm/sun4  sun4

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

FILES

/etc/hosts hosts database

/etc/ethers database of hostnames and Ethernet addresses

/usr/etc/ndbootd ND boot block server

/etc/bootparams boot parameter database

/etc/exports database of exported file systems

SEE ALSO

exportfs(8), setup_exec(8), suninstall(8)

Installing the SunOS

DIAGNOSTICS

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

invalid operation type “op”. 
Valid operations are add and remove. 

invalid yp type “yp_type”. 
Valid YP types are master, slave, client, none. 

can’t set up client “clientname”

kvmpath/boot doesn’t exist
The directory for the client’s kernel architecture is not correctly set up. In particular, the directtory, boot is missing. 

can’t set up client “clientname”

execpath/boot doesn’t exist
The directory for the client’s application architecture is not correctly set up. In particular, the directtory, boot is missing. 

invalid tape device
Valid tape devices are ar, st, mt and xt. 

incorrect number of arguments
All 10 arguments are required. Check number and order of the arguments.

client “clientname” already exists
You cannot add a client with the same name as an existing client.

client “clientname” does not exist
You can not remove a client that does not exist.

invalid architecture type “arch”

can’t obtain ip address from Yellow Pages for “clientname”
The command ‘ypmatch clientname hosts’ failed. 

can’t find ip address in /etc/hosts for “clientname”
The name clientname could not be found in /etc/hosts. 

can’t find address in /etc/ethers for “clientname”
The name clientname could not be found in /etc/ethers. 

can’t obtain ether address from Yellow Pages for “clientname”
The command ‘ypmatch clientname ethers’ failed. 

invalid tape host
The remote tape host’s name could not be found in /etc/hosts or in the YP hosts file. 

invalid tape drive type
Valid tape types are local and remote. 

ATTENTION: /etc/bootparams on the yp master needs to be updated
The /etc/bootparams file on the YP master needs to be updated with the information for the client being installed.  This message displayed when installing a client on a machine other than a YP master. 

ATTENTION: mkfile does not exist. 

ATTENTION: swapsize bytes of swap for clientname not created
The command /usr/etc/mkfile is missing. 

ATTENTION: boot.arch not created

ATTENTION: HEXADDR −> boot.arch not created
The boot file for arch arch in the /tftpboot directory does not exist.  The tftpboot symbolic link for the client could not be created.  This is not a fatal error.  This message does not apply to Sun386i systems. 

ATTENTION: boot.S386 doesn’t exist

ATTENTION: HEXADDR −> boot.S386 not created. 
The boot file for arch sun386 in the /tftpboot directory does not exist.  The tftpboot symbolic link for the Sun386i client could not be created.  This is not a fatal error.  This message applies only to Sun386i systems. 

ATTENTION: /etc/exports needs attention ! 

ATTENTION: fix /etc/exports and rerun exportfs ! 
After updating /etc/exports to export the client’s root, swap or home directories, the ‘/usr/etc/exportfs −a’ command failed.  This is not a fatal error. 

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.

Sun Release 4.0  —  Last change: 2 May 1989