Simple Process job

This is a job for directly controlling processes without an init script.

This is useful when the service has no init script, or the system has no concept of init scripts (e.g. Windows).

This job has the following configuration parameters:


Must be process.


The full path of the binary to start. If not given, defaults to the job name.


Additional arguments to pass to the binary. They will be split in a shell-like fashion, i.e., you can use quotes to include spaces in one argument. If not given, no arguments are passed.


If yes, treat this process as a “one-shot” process, which is supposed to be started and then stop after doing it job. The only effects of this flag are that the service returns “NOT RUNNING” (instead of “DEAD”) when not running, and that the output is caught by Marche if outputfile is not set. It can be retrieved by the “get output” command.

The default is “no”.


The initial working directory for the process. If not given, Marche’s working directory is used, which depends on how the daemon was started.


If given, the full path to a file where stdout and stderr from the process will be written to. If not given, Marche’s stdout is used.


If yes, the process will be started when the Marche daemon is started. The default is not to start the process automatically.


Comma-separated full paths of logfiles to read and show to the client when requested. If not given, the outputfile is the default.


Comma-separated full paths of config files to transfer to the client and write back when updates are received. If not given, no configs are transferred.


A nicer description for the job, to be displayed in the GUI. Default is no description, and the job name will be displayed.


The standard parameters present for all jobs.

A typical section looks like this:

type = process
binary = MyProcess
workingdir = /tmp
outputfile = /var/log/myprocess.log