Page History

...

Security Configuration File: `private.conf`

`js7`	`job`	`execution`
			`signed-script-injection-allowed`	`<yes>\|<no>`

By default the Agent prevents any commands and scripts from being executed except for scripts located in specific directories. This setting allows any commands and scripts to be executed that the workflow has signed and the signature has been verified.

`js7`	`job`	`execution`		Default
			`kill-with-sigterm-command`	`"/bin/kill", "$pid"`
			`kill-with-sigkill-command`	`"/bin/kill", "-KILL", "$pid"`

The Agent can be instructed to terminate running jobs, see JS7 - FAQ - Does JS7 reliably kill running jobs?
The following settings are in place to terminate running jobs by an Agent operated for a Unix OS:
- The setting kill-with-sigterm-command specifies the OS command executed by the Agent to forward a SIGTERM signal to the running job.
- The setting kill-with-sigkill-command specifies the OS command executed by the Agent to forward a SIGKILL signal to the running job.
Both settings are specified as an array of arguments, i.e. "/bin/kill", "-KILL", "$pid" translates to the command: /bin/kill -KILL 99 provided that 99 were the Process ID of the running job.
This setting can be applied should the Agent be operated for an OS that makes use of a different syntax for the kill command.

...