Knowledge Center         Contents    Previous  Next    Index  
Platform Computing Corp.

bladmin

reconfigures the Platform LSF License Scheduler daemon (bld)

Synopsis

bladmin subcommand 
bladmin [-h | -V] 

Description

Use this command to reconfigure the License Scheduler daemon (bld).

You must be a License Scheduler administrator to use this command.

Subcommand List

ckconfig [-v] 
reconfig [host_name ... | all] 
shutdown [host_name ... | all] 
blddebug [-c class_name ...] [-l debug_level] [-f logfile_name] [-o] 
blcdebug [-l debug_level] [-f logfile_name] [-o] collector_name ... 
| all 
-h 
-V 

Options

ckconfig [-v]

Checks LSF License Scheduler configuration in LSF_ENVDIR/lsf.licensescheduler and lsf.conf.

By default, bladmin ckconfig displays only the result of the configuration file check. If warning errors are found, bladmin prompts you to use the -v option to display detailed messages.

-v

Verbose mode. Displays detailed messages about configuration file checking to stderr.

reconfig [host_name ... | all]

Reconfigures License Scheduler.

shutdown [host_name ... | all]

Shuts down License Scheduler.

blddebug [-c class_name ...] [-l debug_level] [-f logfile_name] [-o]

Sets the message log level for bld to include additional information in log files. You must be root or the LSF administrator to use this command.

If the bladmin blddebug is used without any options, the following default values are used:

-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 lsf.h.

Valid log classes:

Default: 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 levels.

Possible values:

0 LOG_DEBUG level in parameter LS_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 LS_LOG_MASK)

-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.

Default: 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 back to the default log file.

blcdebug [-l debug_level] [-f logfile_name] [-o] collector_name | all

Sets the message log level for blcollect to include additional information in log files. You must be root or the LSF administrator to use this command.

If the bladmin blcdebug is used without any options, the following default values are used:

-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 levels.

Possible values:

0 LOG_DEBUG level in parameter LS_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 LS_LOG_MASK)

-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.

Default: 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 back 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. all 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


Platform Computing Inc.
www.platform.com
Knowledge Center         Contents    Previous  Next    Index