bladmin
Administrative tool for IBM® Spectrum LSF License Scheduler.
Synopsis
bladmin subcommandDescription
The bladmin command provides a set of subcommands to control LSF License Scheduler.
You must be root or a LSF License Scheduler administrator to use this command.
Subcommand synopsis
ckconfigUsage
- ckconfig
- Checks LSF License Scheduler
configuration in the LSF_ENVDIR/lsf.licensescheduler and
lsf.conf files.
By default, the bladmin ckconfig command displays only the result of the configuration file check. If warning errors are found, the bladmin command prompts you to enter the y option to display detailed messages.
- reconfig [host_name ... | all]
- Reconfigures LSF License Scheduler.
- shutdown [host_name ... | all]
- Shuts down LSF License Scheduler.
- blddebug [-c class_name ...] [-l debug_level] [-f logfile_name] [-o]
- Sets the message log level for the bld daemon to include extra information in
log files. You must be root or the LSF
administrator to use this command.If the bladmin blddebug command is used without any options, the following default values are used:
- class_name=0
- No additional classes are logged.
- debug_level=0
- LOG_DEBUG level in the LS_LOG_MASK parameter.
- logfile_name=daemon_name.log.host_name
- Current LSF system log file in the LSF system log file directory.
- -c class_name ...
- Specifies software classes for which debug messages are to be logged.
Format of class_name is the name of a class, or a list of class names separated by spaces and enclosed in quotation marks. Classes are also listed in the lsf.h file.
The following log classes are supported:- LC_AUTH
- Log authentication messages.
- LC_COMM
- Log communication messages.
- LC_FLEX
- Log everything that is related to FLEX_STAT or FLEX_EXEC Flexera APIs.
- LC_LICENCE
- Log license management messages.
- LC_PREEMPT
- Log preemption policy messages.
- LC_RESREQ
- Log resource requirement messages.
- LC_TRACE
- Log significant program walk steps.
- LC_XDR
- Log everything that is transferred by XDR.
The default debug level is 0 (no additional classes are logged).
- -l debug_level
- Specifies level of detail in debug messages. The higher the number, the more detail that is
logged. Higher levels include all lower logging levels. For example,
LOG_DEBUG3 includes LOG_DEBUG2
LOG_DEBUG1, and LOG_DEBUG levels.The following values are supported:
- 0
- LOG_DEBUG level in parameter LS_LOG_MASK in the lsf.conf file. This is the default value.
- 1
- LOG_DEBUG1 level for extended logging.
- 2
- LOG_DEBUG2 level for extended logging.
- 3
- LOG_DEBUG3 level for extended logging.
- -f logfile_name
- Specifies the name of the file where debugging messages are logged. The file name can be a full
path. If a file name without a path is specified, the file is saved in the LSF system
log directory.
The name of the file has the following format:
logfile_name.daemon_name.log.host_name
On UNIX, if the specified path is not valid, the log file is created in the /tmp directory.
On Windows, if the specified path is not valid, no log file is created.
The default is the current LSF system log file in the LSF system log file directory.
- -o
- Turns off temporary debug settings and resets them to the daemon starting state. The message log level is reset back to the value of LS_LOG_MASK and classes are reset to the value of LSB_DEBUG_BLD. The log file is also reset to the default log file.
- blcdebug [-l debug_level] [-f logfile_name] [-o] collector_name | all
- Sets the message log level for the blcollect command to include additional
information in log files. You must be root or the LSF
administrator to use this command.If the bladmin blcdebug command is used without any options, the following default values are used:
- debug_level=0
- The LOG_DEBUG level in the LS_LOG_MASK parameter.
- logfile_name=daemon_name.log.host_name
- Current LSF system log file in the LSF system log file directory.
- collector_name=default
- The default collector name.
- -l debug_level
- Specifies level of detail in debug messages. The higher the number, the more detail that is
logged. Higher levels include all lower logging levels. For example,
LOG_DEBUG3 includes LOG_DEBUG2
LOG_DEBUG1, and LOG_DEBUG levels.The following values are supported:
- 0
- LOG_DEBUG level in parameter LS_LOG_MASK in the lsf.conf file. This is the default value.
- 1
- LOG_DEBUG1 level for extended logging.
- 2
- LOG_DEBUG2 level for extended logging.
- 3
- LOG_DEBUG3 level for extended logging.
- -f logfile_name
- Specifies the name of the file where debugging messages are logged. The file name can be a full
path. If a file name without a path is specified, the file is saved in the LSF system
log directory.
The name of the file has the following format:
logfile_name.daemon_name.log.host_name
On UNIX, if the specified path is not valid, the log file is created in the /tmp directory.
On Windows, if the specified path is not valid, no log file is created.
The default is the current LSF system log file in the LSF system log file directory.
- -o
- Turns off temporary debug settings and resets them to the daemon starting state. The message log
level is reset back to the value of LS_LOG_MASK and classes are reset
to the value of LSB_DEBUG_BLD. The log file is also reset to the
default log file.
If a collector name is not specified, default value is to restore the original log mask and log file directory for the default collector.
- collector_name ... | all
- Specifies the collector names, separated by blanks. The all keyword means all the collectors.
- -h
- Prints command usage to stderr and exits.
- -V
- Prints release version to stderr and exits.
See also
blhosts, lsf.licensescheduler, lsf.conf