man volserver (Administration système) - Initializes the Volume Server component of the fs process

NAME

volserver - Initializes the Volume Server component of the fs process

SYNOPSIS

volserver [-log] << [-p <number of processes] >>> << [-udpsize <size of socket buffer in bytes] >>> [-enable_peer_stats] [-enable_process_stats] [-help]

DESCRIPTION

The volserver command initializes the Volume Server component of the CWfs process. In the conventional configuration, its binary file is located in the /usr/lib/openafs directory on a file server machine.

The volserver command is not normally issued at the command shell prompt but rather placed into a file server machine's /etc/openafs/BosConfig file with the bos create command. If it is ever issued at the command shell prompt, the issuer must be logged onto a database server machine as the local superuser CWroot.

The Volume Server records a trace of its activity in the /var/log/openafs/VolserLog file. Use the bos getlog command to display the contents of the file.

The Volume Server processes the vos commands that administrators use to create, delete, move, and replicate volumes, as well as prepare them for archiving to tape or other media.

By default, the VL Server runs nine lightweight processes (LWPs). To change the number, use the -p argument.

This command does not use the syntax conventions of the AFS command suites. Provide the command name and all option names in full.

OPTIONS

Records in the /var/log/openafs/VolserLog file the names of all users who successfully initiate a vos command. The Volume Server also records any file removals that result from issuing the vos release command with the -f flag. Sets the number of server lightweight processes (LWPs) to run. Provide an integer between CW4 and CW16. The default is CW9. Sets the size of the UDP buffer in bytes, which is 64 KB by default. Provide a positive integer, preferably larger than the default. Activates the collection of Rx statistics and allocates memory for their storage. For each connection with a specific UDP port on another machine, a separate record is kept for each type of RPC (FetchFile, GetStatus, and so on) sent or received. To display or otherwise access the records, use the Rx Monitoring API. Activates the collection of Rx statistics and allocates memory for their storage. A separate record is kept for each type of RPC (FetchFile, GetStatus, and so on) sent or received, aggregated over all connections to other machines. To display or otherwise access the records, use the Rx Monitoring API. Prints the online help for this command. All other valid options are ignored.

EXAMPLES

The following bos create command creates a CWvolserver process on the machine CWfs2.abc.com:

   % bos create -server fs2.abc.com -instance volserver -type simple \
                 -cmd /usr/lib/openafs/volserver

PRIVILEGE REQUIRED

The issuer must be logged in as the superuser CWroot on a file server machine to issue the command at a command shell prompt. It is conventional instead to create and start the process by issuing the bos create command.

SEE ALSO

the BosConfig(5) manpage, the VolserLog(5) manpage, the bos_create(8) manpage, the bos_getlog(8) manpage, the vos(1) manpage

COPYRIGHT

IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.