You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
crontabs in general are not meant to go down to seconds however there are some rare cases where this is a requirement.
On traditional crontab you can achieve this e.g. adding a sleep 15 before the command to run. I could replicate this with a delay 15000/30000/45000, however a control on the number of seconds (now) would be perfect. e.g. a "wait"
Please note I'm not talking about the main trigger, I actually run my script manually, I need some loops in the script to eventually align to those seconds.
So in short: could we have a more granular control on the triggers? In my particular scenario I need to run 1 script at second 0s and 30s, and a script 2 at 15s and 45s.
Thanks
The text was updated successfully, but these errors were encountered:
crontabs in general are not meant to go down to seconds however there are some rare cases where this is a requirement.
On traditional crontab you can achieve this e.g. adding a sleep 15 before the command to run. I could replicate this with a delay 15000/30000/45000, however a control on the number of seconds (now) would be perfect. e.g. a "wait"
Please note I'm not talking about the main trigger, I actually run my script manually, I need some loops in the script to eventually align to those seconds.
So in short: could we have a more granular control on the triggers? In my particular scenario I need to run 1 script at second 0s and 30s, and a script 2 at 15s and 45s.
Thanks
The text was updated successfully, but these errors were encountered: