Purpose
Prints a server process's log file
Synopsis
bos getlog -server <machine name> -file <log file to examine> [-cell <cell name>] [-noauth] [-localauth] [-help] bos getl -s <machine name> -f <log file to examine> [-c <cell name>] [-n] [-l] [-h]
Description
The bos getlog command displays on the standard output stream the specified log file from the machine named by the -server argument. The BOS Server fetches the log file from the /usr/afs/logs directory unless an alternate pathname is provided as part of the -file argument.
Cautions
Log files can grow quite large, especially for the database server processes. To keep them to a manageable size, periodically either use the UNIX rm command to truncate each log file, or use the bos restart command to restart each process.
It can take up to five minutes after the file is removed or process restarted for the space occupied by a log file to become available.
Options
If a pathname and filename are provided, the log file is retrieved from the indicated directory. Partial pathnames are interpreted relative to the /usr/afs/logs directory.
Output
The output is preceded by the line
Fetching log file 'filename'...
The remainder of the output depends on the particular log file.
Examples
The following example displays the FileLog file from the machine fs3.abc.com:
% bos getlog -server fs3.abc.com -file FileLog Fetching log file 'FileLog'... Sun Nov 8 04:00:34 1998 File server starting Sun Nov 8 04:00:39 1998 Partition /vicepa: attached 21 volumes; 0 volumes not attached Sun Nov 8 04:00:40 1998 File Server started Sun Nov 8 04:00:40 1998 Mon Nov 9 21:45:06 1998 CB: RCallBack (zero fid probe in host.c) failed for host 28cf37c0.22811
Privilege Required
The issuer must be listed in the /usr/afs/etc/UserList file on the machine named by the -server argument, or must be logged onto a server machine as the local superuser root if the -localauth flag is included.
Related Information