diff options
author | Bruno Randolf <br1@einfach.org> | 2020-11-09 10:43:10 +0000 |
---|---|---|
committer | Petr Štetiar <ynezz@true.cz> | 2020-11-12 18:19:44 +0100 |
commit | 7185c5ec7d357897c1379234a00570afe2ee9eff (patch) | |
tree | 2a5738a7094f9f91109cf378301a56f0db6a6dd7 /package/utils/busybox/files | |
parent | dd993e28eff0ee0fed8abf139e280aa04c0626f6 (diff) | |
download | upstream-7185c5ec7d357897c1379234a00570afe2ee9eff.tar.gz upstream-7185c5ec7d357897c1379234a00570afe2ee9eff.tar.bz2 upstream-7185c5ec7d357897c1379234a00570afe2ee9eff.zip |
busybox: Let procd respawn cron
On some systems I see the issue that crond dies after a few days.
Simply letting procd respawn the process is a simple safety-net.
Signed-off-by: Bruno Randolf <br1@einfach.org>
Diffstat (limited to 'package/utils/busybox/files')
-rwxr-xr-x | package/utils/busybox/files/cron | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/package/utils/busybox/files/cron b/package/utils/busybox/files/cron index ca04a0c170..4efdfa52ca 100755 --- a/package/utils/busybox/files/cron +++ b/package/utils/busybox/files/cron @@ -32,6 +32,7 @@ start_service() { for crontab in /etc/crontabs/*; do procd_set_param file "$crontab" done + procd_set_param respawn procd_close_instance } |