commands – job start/kill
Start/kill a job.
Usage
job [force] start name
job kill name
where
| force | start a job even if their conditions are not met. |
| start | job. |
| kill | a running job. |
| name | of job to start or kill. |
execute on name
stateful jobs are not currently implemented.
Examples
Start a job
BeyondCron % job start /examples/server/backup
BeyondCron % job status $$
Job State Result ----------------------- ------- ------- /examples/server/backup Running Unknown
Kill a job
BeyondCron % job kill backup
BeyondCron % job status $$
Job State Result ----------------------- --------- ------ /examples/server/backup Scheduled Killed
Attempt start a disabled job
BeyondCron % job start /examples/server/reboot
Job /examples/server/reboot is disabled
Attempt to start a job with one or more un-met start conditions
BeyondCron % job start /examples/server/reboot
One or more conditions not met for job /examples/server/reboot
BeyondCron % job status $$
Job State Result ----------------------- ------- ------- /examples/server/backup Running Unknown
In this case the job reboot requires that the job backup is stopped.
Force start a job with one or more un-met start conditions
BeyondCron % job force start /examples/server/reboot
BeyondCron % job status /examples/server
Job State Result ----------------------- ------- ------- /examples/server/backup Running Unknown /examples/server/reboot Running Unknown
See also
- job add
- job calendar
- job changes
- job command
- job condition
- job content
- job copy
- job delay
- job delete
- job description
- job diff
- job email
- job enable/disable/bypass
- job history
- job host
- job image
- job input
- job list
- job message
- job output
- job property
- job schedule
- job show
- job sql
- job status
- job subject
- job timezone
- job trigger
- job url
- job user
- job variables