Site daemons from the command line

To run or modify Site Daemons from the command line, open a shell window and use the hcisitectl command.

hcisitectl [-f] [-h host] [{ -K | -k daemon }] [-v] 
[{ -S | -s daemon}] [{ -R | -r daemon} -d delay interval] 
[-u #users] [-A args] [-n]
  • -f forces stopping the daemons.
  • -h host is the name of the remote host.
  • -K stops all daemon processes.
  • -k daemon stops the specified daemon.. For daemon, use a comma-separated list if specifying multiple daemons, where:
    • l is the Lock Manager.
    • m is the Monitor Daemon.
  • -v checks for duplicate hcimonitord when starting/stopping MonitorD, preventing duplicate MonitorDs in one site.
  • -S starts all daemon processes.
  • -s daemon starts the specified daemon. For daemon, use a comma-separated list if specifying multiple daemons, where:
    • l is the Lock Manager.
    • m is the Monitor Daemon.
  • -R restarts all daemon processes and is used with -d delay interval.
  • -r daemon restarts the specified daemon and is used with -d delay interval. For daemon, use a comma-separated list if specifying multiple daemons, where:
    • l is the Lock Manager.
    • m is the Monitor Daemon.
  • -d delay interval is the time interval for engine restarting.
  • -u #users is the maximum number of users for Lock Manager. #users defaults to 500 and must be greater than 200.
  • -A args specifies the startup arguments for the daemons. For args, use a comma-separated list if specifying multiple arguments. Each entry has the form daemon = args, where:
    • l args is the Lock Manager, followed by arguments.
    • m args is the Monitor Daemon, followed by arguments.
    • args are the arguments to pass to that daemon.
  • -n specifies to not run the engine in a service on Windows.

If no options are specified, then the status of the daemons is verified and reported.

Note: Do not stop the Lock Manager without first ensuring that there are no running engine processes in the site.