Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow triggers/loops to understand seconds #1918

Open
wellloaded opened this issue Feb 27, 2025 · 0 comments
Open

allow triggers/loops to understand seconds #1918

wellloaded opened this issue Feb 27, 2025 · 0 comments

Comments

@wellloaded
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant