The following instructions can help you use the bos status command to determine which server machines are filling the various machine roles in your cell or domain. The instructions assume that your cell is configured according to the installation and configuration instructions for your system; for example, they assume that all machines except the System Control machine are running a client portion of the Update Server that references the dcelocal/var/dfs directory on the System Control machine. If your server machines are not configured in this manner, these instructions may not help you determine the roles of the machines.
To determine whether a server machine is a System Control machine, a Binary Distribution machine, or neither of the two types of machines, issue the bos status command on the machine with upserver as the argument for the -process option. The output from the command indicates only whether the machine is a System Control machine, a Binary Distribution machine, or neither of the two; a machine that fits neither of the two roles can be a File Server machine, a Fileset Database machine, a Backup Database machine, or any combination of the three.
To learn which machine is the System Control machine, issue the bos status command on any server machine, using upclient as the argument for the -process option. The output for the upclient process used to obtain administrative lists from the System Control machine includes the upclient command used to start the process. The first parameter of the command is the name of the System Control machine; the second parameter is the pathname to the administrative lists on that machine; for example, dcelocal/var/dfs.
To learn which machine is a Binary Distribution machine, issue the bos status command on a server machine of the CPU/OS type you wish to check, again using upclient as the argument for -process. The output for the upclient process used to obtain binary files from the Binary Distribution machine includes the upclient command used to start the process. The first parameter of the command is the name of the Binary Distribution machine; the second parameter is the pathname to the binary files on that machine; for example, dcelocal/bin.
When using the bos status command to determine machine roles, always use the -long option to display more detailed information about the specified processes. You must use the -long option to determine the exact role of a server machine.
The following examples illustrate how to determine whether a machine is a System Control machine or a Binary Distribution machine. The output for a server machine that is neither a System Control machine nor a Binary Distribution machine displays that no upserver is running.
$ bos status /.../abc.com/fs1 upserver -long
bos: failed to get instance info for `upserver' (no such entity)
The output for a System Control machine includes references to the upserver process and the dcelocal/var/dfs directory, where administrative lists are stored.
$ bos status /.../abc.com/fs2 upserver -long
Instance upserver, (type is simple) currently running normally.
Process last started at Mon Nov 4 05:23:54 1991 (1 proc starts)
Parameter 1 is `dcelocal/bin/upserver dcelocal/var/dfs'
The output for a Binary Distribution machine includes references to the upserver process and the dcelocal/bin directory, where binary files for processes and programs are stored.
$ bos status /.../abc.com/fs3 upserver -long
Instance upserver, (type is simple) currently running normally.
Process last started at Mon Nov 4 05:16:31 1991 (1 proc starts)
Parameter 1 is `dcelocal/bin/upserver dcelocal/bin'