diff options
| author | Dale Mellor <mcron-lsfnyl@rdmp.org> | 2023-03-18 14:18:17 +0000 |
|---|---|---|
| committer | Dale Mellor <mcron-lsfnyl@rdmp.org> | 2023-03-18 14:18:17 +0000 |
| commit | 0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6 (patch) | |
| tree | 2cf2ffe793211a8c48ff86a9db57b156f2cddd88 /src/mcron/scripts/cron.scm | |
| parent | fd19e63490e30fb5ae4cc159f72b8f40952ceb9d (diff) | |
| parent | 4727c770c2a723d46b4162cff21ab8f0b75c3998 (diff) | |
| download | mcron-0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6.tar.gz mcron-0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6.tar.bz2 mcron-0fe4d2cc9544d24ecc3e74a2d92433e01b9e25c6.zip | |
Merge system-wide Vixie cron updates.
I don't believe that anyone should be running system-wide cron processes these
days (the attack surface is rather large), but should use separate per-user or
per-service mcron daemon processes. But mcron is advertised as a drop-in
Vixie replacement, so we should do what we can to make it safe in this use
case.
I've performed a basic vetting of the changes against vandalism, but haven't
verified the correctness of the code or done any checking; the changes are
being accepted on the basis that almost anything is an improvement on what
currently exists.
Diffstat (limited to 'src/mcron/scripts/cron.scm')
| -rw-r--r-- | src/mcron/scripts/cron.scm | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mcron/scripts/cron.scm b/src/mcron/scripts/cron.scm index 2e36d87..3c3a57c 100644 --- a/src/mcron/scripts/cron.scm +++ b/src/mcron/scripts/cron.scm @@ -147,7 +147,7 @@ option.\n") (delete-file config-socket-file)) noop) (exit EXIT_FAILURE)))) - '(SIGTERM SIGINT SIGQUIT SIGHUP)) + (list SIGTERM SIGINT SIGQUIT SIGHUP)) ;; We can now write the PID file. (with-output-to-file config-pid-file |