admclient(1M) DG/UX R4.11MU05 admclient(1M)
NAME
admclient - manage operating system clients
SYNOPSIS
admclient -o add -r release [ -S server ] [ -b bootstrap ] [ -h
home_directory ] [ -k kernel ] [ -s swap_size ] ] [ -C ] [
-d device_name ] hostname ...
admclient -o delete -r release [ -p ] hostname ...
admclient -o list [ -qv ] [ hostname ... ]
admclient -o modify -r release [ -b bootstrap ] hostname ...
admclient -o set -r release [ -S server ] hostname ...
DESCRIPTION
The admclient command is run on the server machine to manage client
machines that are served by the server. A client is any machine
which gets operating system software from another machine. Disk
areas are set aside on the server for use by the clients and
configuration files within those areas are initialized for correct
use by the clients. Database entries are made on the server to keep
track of the state and configuration of each client.
Operations
add Add an OS client to a release area on the server by
creating the client's directory structure, client database
table entries, and updating files accessible to the client.
A client may be added to more than one release. The client
must be added to the hosts database (using admhost(1M)) and
the ethers database (using admether(1M)) before being added
as a client.
As part of the add operation the release area's
usr/root.proto files are copied into the client's root.
You can suspend copying of the root.proto files by using
the option -O noproto.
delete Remove an OS client from a release area on the server by
updating the server's database and optionally removing the
disk areas allocated for the client.
list Display information about all or selected OS clients.
modify Change the bootstrap file used for an OS client.
set Change the release area in which an OS client will boot.
The release area name can be specified as ``-none-'' to
keep a client from booting from any release area.
Options
-b bootstrap
The pathname of the bootstrap file. The default bootstrap
file is /usr/stand/boot.aviion.
-C Add a client to an existing release area as a cluster node.
The release area must already exist on the system and its
databases must be mounted under /srv as a dg/cfs file
system. The client must be added to the hosts database and
the ethers database before being added as a client.
Client specific, release specific directory space (root
file systems) are created in the release area's directory
space if definitions for these are contained in the release
area definition or the client definition. By default the
admrelease -o name_primary operation will create
definitions for these file systems based on the mount
points and sizes that exist on the OS server when the
operation is executed. Any clients added to the named
PRIMARY area will pickup these definitions.
-d device_name
The physical disk device name on which the new root virtual
disk is to be created.
-h home_directory
The directory in which users' home directories will be
placed. If not the special value ``none'', the directory
will be created on the server and exported to the client.
-k kernel The pathname of the kernel file. The default kernel file
for the PRIMARY release area is
/srv/release/PRIMARY/root/_Kernels/dgux.diskless.
-O options
This option specifies secondary options that are used to
control the behavior of an operation.
proto | noproto
For the add operation, noproto specifies that the
root.proto of the target release area should not be
recopied to the target root as part of the copy
operation. The default setting for this option is proto.
You may explicitly set the option to proto.
-p Preserve the client's root directory structure when
deleting a client.
-q Quiet. Omit header lines from the output of the list
operation.
-r release
The name of the release area. Clients may be associated
with more than one release area; this identifies which
instance of the client that is to be affected.
-s swap_size
The size of the swap area to create for the client. The
default value is 16m.
-S server
The name of the server machine as known to the client.
This defaults to the default host name as returned by the
hostname(1) command.
-v Verbose. Include header lines in the output of the list
operation. This option is enabled by default.
OUTPUT
If a particular client name or list of client names is provided to
the list operation, the output includes the following: client host
name, release area name, root directory, swap file, swap size, boot
file, and kernel file.
If no hostnames or the keyword ``all'' is specified, the output
includes each client name and release area. Unless the -q option is
used, header line is produced.
FILES
/srv/release/PRIMARY/root/_Kernels/dgux.diskless
The default kernel file.
/usr/stand/boot.aviion The default bootstrap file.
/home The default for the home directory
pathname.
/tftpboot Directory containing bootstrap file
links for each client.
DIAGNOSTICS
Warnings
- A database file could not be updated.
Errors
- A prototype file was missing.
- The host name is not recognized.
Exit Codes
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions. You must
have appropriate privilege to perform the add, delete, modify,
and set operations. 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 the cap_defaults(5) man page
for more information that pertains to systems with DG/UX
information security.
On systems without the DG/UX Capability Option, appropriate
privilege means that your process has an effective UID of
root. See the appropriate_privilege(5) man page for more
information.
3 There was an error in the command line.
SEE ALSO
admether(1M), admhost(1M), admrelease(1M), sysadm(1M).
appropriate_privilege(5).
Licensed material--property of copyright holder(s)