The following options and arguments are used with many of the commands described in this topic. If an option or argument is not described with a command in the text, a description of it appears here. (See Part 2 of this guide and reference for complete details about each command.)
· The -server machine option specifies the server machine on which the command is to execute. This option names the machine whose process or file is to be affected. The BOS Server on this machine executes the command. This option can be used to specify a server machine in a foreign cell.
To run a privileged bos command (a bos command that requires the issuer to have some level of administrative privilege) using a privileged identity, always specify the full DCE pathname of the machine (for example, /.../abc.com/hosts/fs1).
To run an unprivileged bos command, you can use any of the following to specify the machine:
- The machine's DCE pathname (for example, /.../abc.com/hosts/fs1)
- The machine's host name (for example, fs1.abc.com or fs1)
- The machine's IP address (for example, 11.22.33.44)
Note: If you specify the host name or IP address of the machine, the command executes using the unprivileged identity nobody (the equivalent of running the command with the -noauth option); unless DFS authorization checking is disabled on the specified machine, a privileged bos command issued in this manner fails. If you specify the machine's host name or IP address, the command displays the following message (using the -noauth option suppresses the message):
bos: WARNING: short form for server used; no authentication
information will be sent to the bosserver
· The -process server_process option is the process to be created, started, or stopped. The following names are recommended for DFS server processes, but a process can be given any name:
- ftserver: The Fileset Server process
- flserver: The Fileset Location Server process
- upclient: The client portion of the Update Server that transfers binary files (such as those for server processes) from dcelocal/bin and transfers configuration files (such as administrative lists) from dcelocal/var/dfs on the System Control machine
- upserver: The server portion of the Update Server
- repserver: The Replication Server process
- bakserver: The Backup Server process
· The -cmd cmd_line option specifies the commands and parameters that the BOS Server uses to create a process. For a simple process, only one command line specifying the binary file's complete pathname is necessary. This can be the pathname of a DFS command or any other command to be executed. For example, the command "dcelocal/bin/fts clonesys" backs up every fileset in the file system. As this example shows, you must enclose the parameter in " " (double quotes) if it contains spaces, and you must specify the complete pathname for the command.
For a cron process, cmd_line specifies the following two command parameters:
- The first parameter is the command that the BOS Server executes. As with the sole parameter for a simple process, this parameter can be the complete pathname of the binary file for a DFS command or any other command to be executed. As the example for the simple process shows, you must enclose the parameter in double quotes if it contains spaces, and you must specify the complete pathname for the command.
- The second parameter specifies the time at which the BOS Server is to execute the command. This parameter must also be surrounded with double quotes if it contains spaces. Valid values are
- never. The command does not execute, but the process entry remains in the BosConfig file.
- now. The command executes immediately, but it never executes again; the process entry is removed from the BosConfig file after the command is executed.
- A specific day of the week at a specific time ("day hh:mm"). The command executes weekly at the specified day and time.
- A specific time (hh:mm). The command executes daily at the specified time.
If you specify a day, it must appear first, in lowercase letters. You can enter either the entire name or just the first three letters; for example, sunday or sun. When indicating a time, separate hours from minutes with a colon. You can use 24-hour time or 1:00 through 12:00 with am or pm (for example, 14:30 or "2:30 pm"). You must enclose the entry in " " (double quotes) if it contains spaces (for example, "sun 2:30 pm").
· The -noauth option directs the bos program to use the unprivileged identity nobody as the identity of the issuer of the command. If DFS authorization checking has been disabled with the bos setauth command, the identity nobody has the necessary privileges to perform any operation. (See Using Administrative Lists and Keytab Files for information about disabling DFS authorization checking.) If you use this option, do not use the -localauth option.
· The -localauth option directs the bos program to use the DFS server principal of the machine on which the command is issued as the identity of the issuer. Each DFS server machine has a DFS server principal stored in the Registry Database. A DFS server principal is a unique, fully qualified principal name that ends with the string dfs-server; for example, /.../abc.com/hosts/fs1/dfs-server. Do not confuse a machine's DFS server principal with its unique self identity. (See Making Filesets and Aggregates Available for information about DFS server principals.)
Use this option only if the command is issued from a DFS server machine. You must be logged into the server machine as root for this option to work. If you use this option, do not use the -noauth option.
The -noauth and -localauth options are always optional.