Enter the bos status command to check the statuses of the processes on a server machine. Use the -process option to display the statuses of specific processes on the specified server machine, or omit the option to display the statuses of all processes on the machine.
$ bos status -server machine [-process server_process...] [-long]
The -long option indicates that more detailed information about the specified processes is to be displayed.
The command first displays the following line if DFS authorization checking is disabled on the machine (it does not display the line if DFS authorization checking is enabled):
Bosserver reports machine is not checking authorization.
It then displays the following line if the BOS Server finds that the dcelocal directory or a directory or file beneath it on the machine has protections that the BOS Server believes are inappropriate:
Bosserver reports inappropriate access on server directories.
The BOS Server displays this message if the UNIX mode bits on the dcelocal directory and its contents do not enforce certain protections; for example, the message can indicate that users who should not be able to write to the dcelocal directory and its subdirectories have write access. The BOS Server also displays the message if a directory or file is not owned by the appropriate user (for example, root).
The BOS Server displays the message as a courtesy to the user. It does nothing to change the protections, nor does it fail if the protections are violated. (See the description of the bos status command in Part 2 of this guide and reference for information about the protections the BOS Server wants to see enforced.)
Note: Your vendor can modify the default protections enforced by the BOS Server. Refer to your vendor's documentation to determine the protections that apply for your version of DFS.
The command then displays status information about the processes on the machine. The possible statuses for any process include
· currently running normally - For a simple process, this means it is currently running; for a cron process, this means it is scheduled to run.
· temporarily enabled - The status flag for the process in the BosConfig file is NotRun, but the process has been enabled with the bos startup or bos restart command.
· temporarily disabled - Either the bos shutdown command was used to stop the process, or the BOS Server quit trying to restart the process, in which case the message stopped for too many errors also appears.
· disabled - The status flag for the process in the BosConfig file is NotRun, and the process has not been enabled.
· has core file - The process failed or produced a core file at some time. This message can appear with any of the other messages. Core files are stored in dcelocal/var/dfs/adm. The name of the core file indicates the process that failed; for example, core.ftserver.
The output for a cron process includes an auxiliary status message, reporting when the command is next scheduled to execute.
The following additional information is displayed when the -long option is used:
· The process type (simple or cron).
· How many proc starts occurred; proc starts occur when the process is started or restarted by the current BOS Server.
· The time of the last proc start.
· The exit time and error exit time when the process last failed. This appears only if the process failed while the BOS Server was running. (Provided the BOS Server was running both when the process was started and when it failed, the BOS Server can provide this information for any process that has an entry in the BosConfig file.)
· The command and its options that are used by the BOS Server to start the process.
The following examples show two executions of the bos status command on the same server machine. The first example shows the output displayed when the -long option is omitted from the command.
$ bos status /.../abc.com/hosts/fs4
Instance ftserver, currently running normally.
The second example shows the output displayed when the -long option is included with the command.
$ bos status /.../abc.com/hosts/fs4 -long
Instance ftserver, (type is simple) currently running normally.
Process last started at Fri Nov 22 05:36:02 1991 (1 proc starts)
Parameter 1 is `dcelocal/bin/ftserver'