Services control reference

Muster Services control is a small application that let you configure, start and stop the Muster services installed locally. Muster Services control runs in the taskbar or in the upper bar of the Finder on Mac OS X.

The Services control applet is made by two tabs, one specific to configure and interact with the Render client, and another specific to configure the Dispatcher Service.

The next picture shows the tab specific to the Dispatcher service:

  • Clients listening port: Defines the port where the Dispatcher will listen for Render clients connections
  • Management listening port: Defines the port where the Dispatcher will listen for Console/mrtool connections
  • Databases connections:
    • Queue database engine: The engine to use for the queue data
    • Queue database address: The address of your queue database (only if not using sqlite)
    • Queue database name: The database name of your queue data (if using sqlite, defines the filename for the data)
    • Queue database login: The database login of your queue data (only if not using sqlite)
    • Queue database password: The database password of your queue (only if not using sqlite)
    • History database engine: The engine to use for the history data
    • History database address: The address of your history database (only if not using sqlite)
    • History database name: The database name of your history data (if using sqlite, defines the filename for the data)
    • History database login: The database login of your history data (only if not using sqlite)
    • History database password: The database password of your history (only if not using sqlite)
    • Backup database engine: The engine to use for the backup data
    • Backup database address: The address of your backup database (only if not using sqlite)
    • Backup database name: The database name of your backup data (if using sqlite, defines the filename for the data)
    • Backup database login: The database login of your backup data (only if not using sqlite)
    • Backup database password: The database password of your backup (only if not using sqlite)
  • Install service: Let you install the Dispatcher as a system service
  • Remove service: Let you remove the Dispatcher from system services
  • View Log: Let you view the current dispatcher.log file
  • Edit config: Let you edit the dispatcher.conf file
  • Start service: Starts the Dispatcher service. If the service is not installed as a system service, it will be spawned as a user application inside a logging window. If you close the Services control, the service will be terminated.
  • Stop service: Stops the Dispatcher service.

The next picture shows the tab specific to the Render client service:

  • Dispatcher address: Defines the IP Address or the hostname where the Dispatcher service is installed
  • Dispatcher clients port: Defines the network port where the Dispatcher listens for connections from the Render clients
  • Client management port: Defines the network port where the Render Client listens for management connections
  • Local control: Let you control locally your instances by right clicking on them. Commands meaning may be found looking at the Console reference under the host view section
  • Install service: Let you install the Render client as a system service
  • Remove service: Let you remove the Render client from system services
  • View Log: Let you view the current rc.log file
  • Edit config: Let you edit the rc.conf file
  • Rescan local applications: Let you start the application scanning on the local filesystem to auto configure the paths to render engines available locally
  • Start service: Starts the Render client service. If the service is not installed as a system service, it will be spawned as a user application inside a logging window. If you close the Services control, the service will be terminated.
  • Stop service: Stops the Render client service.