Command Line control of the Job Manager

Users on high-performance clusters can control certain job manager features from the command line.

Option	Effect
--pidfile [Linux only]	Write the job manager's process ID to the file specified in path instead of the default, even if --nodaemon is specified. If this file cannot be written to the job manager will continue without error.
--ipv4 [Not yet for Windows when running as a service]	Communicate using the IPv4 protocol family. This affects only --port (-broadcast is always over IPv4). Can be used in conjunction with --ipv6. The default is to act as though both are specified.
--ipv6 [Not yet for Windows when running as a service]	Communicate using the IPv6 protocol family. This affects only --port. Can be used in conjunction with --ipv4. The default is to act as though both are specified.
--daemon [Linux only]	Detach from the controlling terminal and (if possible) write the job manager's process ID to /var/run/Autodesk/ami2016jm/ami2016jm.pid (or whatever file is named in --pidfile). This is the default. Implies --log.
--nodaemon [Linux only]	Do not detach from the controlling terminal, and do not write the job manager's process ID to /var/run/Autodesk/ami2016jm/ami2016jm.pid (unless --pidfile is also specified). Implies --nolog.
--log [Linux only]	Log messages to the system log facility. This is the default in daemon mode.
--nolog [Linux only]	Do not log messages, but print them to standard error. This is the default in foreground mode.
--distribute-to hostname	Add hostname to the job distribution pool. May be repeated to add several hosts. If omitted, the job manager will attempt to read the list from a persistent configuration file.
--parallel-limit integer	Run no more than this many batch jobs at a time. If omitted, the job manager will attempt to restore the value from a persistent configuration file. Otherwise defaults to 1.
--distribution-parallel-limit integer	Run no more than this many distribution jobs at a time. If omitted, the job manager will attempt to restore the value from a persistent configuration file. Otherwise defaults to 1.
--delete-after duration	Delete temporary files that are older than this many days (append "d" to duration). If omitted, the job manager will attempt to restore the value from a persistent configuration file. Otherwise defaults to "7d".
--default-priority
--tempdir path	Use the directory path to write temporary files to. If not specified, use the directory named in environment variable MFSYN_TMP. If this directory cannot be written to by the job manager user (or if the directory does not exist) the job manager will exit with status 3.

Example

First stop the Job manager daemon which is running in the background:

# /etc/init.d/ami2016jm stop

Then set all the environment variables you need:

# . /etc/opt/Autodesk/ami2016
# export MFSYN_HOME
# export MFSYN_TMP
# export MFSYN_DAT
# export ADSKFLEX_LICENSE_FILE
# [ -n "$MFSYN_JMUSER" ] || MFSYN_JMUSER=root
# export MFSYN_LOG_FACILITY
# export MFSYN_LOG_CHANNEL_OPERATIONAL
# export MFSYN_LOG_CHANNEL_LICENSING
# export MFSYN_LOG_CHANNEL_ANALYTICS
# export MFSYN_LOG_CHANNEL_DEBUG

Then execute the job manager:

# sudo -u $MFSYN_JMUSER /opt/Autodesk/ami2016/bin/mpijm --nodaemon

Each time you restart the Job Manager, you have to stop and restart Synergy for the connection to re-establish.