Description

jobd manages jobs. The format of job configuration files is described in job(5) .

When a new job configuration file is created, jobd will automatically detect this and load the job into memory. By default, the job will be disabled. To enable the job, the jobctl enable command should be executed.

When an existing job configuration file is deleted, jobd will automatically detect this and remove the job from memory. If the job is currently running, it will be stopped.

When an existing configuration file is modified, jobd will automatically detect this and transition the job into the "refresh-needed" state. This alerts the system administrator that the job is running, but with an outdated configuration. is outdated and needs to be refreshed. To refresh the job, the jobctl refresh command should be executed.

OPTIONS

The following options are available:

ENVIRONMENT

When running under a debugger, it is useful to prevent jobd from calling fork(2). This can be done by setting the JOBD_DEBUG_NOFORK environment variable to any non-empty string.

EXIT STATUS

The jobd command exits 0 on success, and >0 if an error occurs

SEE ALSO

jobcfg(1) jobctl(1) job(5)

AUTHORS

Mark Heily <mark@heily.com>