Command Reference Guide

Usage
226 Platform LSF Command Reference
-c "class_name ..."
Specify software classes for which debug messages are to be logged. If a list of classes
is specified, they must be enclosed in quotation marks and separated by spaces.
Possible classes:
LC_AFS - Log AFS messages
LC_AUTH - Log authentication messages
LC_CHKPNT - log checkpointing messages
LC_COMM - Log communication messages
LC_CONF - Print out all parameters in
lsf.conf (and ego.conf
LC_DCE - Log messages pertaining to DCE support
LC_EXEC - Log significant steps for job execution
LC_FILE - Log file transfer messages
LC_HANG - Mark where a program might hang
LC_LICENCE - Log license management messages
LC_MULTI - Log messages pertaining to MultiCluster
LC_PIM - Log PIM messages
LC_SIGNAL - Log messages pertaining to signals
LC_TRACE - Log significant program walk steps
LC_XDR - Log everything transferred by XDR
Default: 0 (no additional classes are logged)-f
NOTE: Classes are also listed in lsf.h.
-l debug_level
Specify level of detail in debug messages. The higher the number, the more detail
that is logged. Higher levels include all lower levels.
Possible values:
0 - LOG_DEBUG level in parameter LSF_LOG_MASK in lsf.conf.
1 - LOG_DEBUG1 level for extended logging. A higher level includes lower logging
levels. For example, LOG_DEBUG3 includes LOG_DEBUG2 LOG_DEBUG1, and
LOG_DEBUG levels.
2 - LOG_DEBUG2 level for extended logging. A higher level includes lower logging
levels. For example, LOG_DEBUG3 includes LOG_DEBUG2 LOG_DEBUG1, and
LOG_DEBUG levels.
3 - LOG_DEBUG3 level for extended logging. A higher level includes lower logging
levels. For example, LOG_DEBUG3 includes LOG_DEBUG2, LOG_DEBUG1, and
LOG_DEBUG levels.
Default:
0 (LOG_DEBUG level in parameter LSF_LOG_MASK)
-f logfile_name
Specify the name of the file into which debugging messages are to be logged. A file
name with or without a full path may be specified.