Schedule a job to run every 10 seconds

[cjboat]

Hello there.

I am trying to do a job that is supposed to run every 10 seconds, but when I import the following into the scheduler, */10 * * * * *, it just sets it at 10 minutes. Am I doing this wrong? Or does Cronicle not support that short of a timeframe?

[jhuckaby]

I'm so sorry, but Cronicle v1 doesn't support seconds. It only goes down to minutes, similar to cron.

Support running jobs on specific seconds, including every 10 seconds, is coming in Cronicle v2! It will be released later this year (2025).

[cjboat]

Is there any way to trick it like I can with regular bash? I am really looking forward to v2!

…

On Mon, Feb 3, 2025 at 3:53 PM Joseph Huckaby ***@***.***> wrote: I'm so sorry, but Cronicle v1 doesn't support seconds. It only goes down to minutes, similar to cron. Support running jobs on specific seconds, including every 10 seconds, is coming in Cronicle v2! It will be released later this year (2025). — Reply to this email directly, view it on GitHub <#857 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA3VT5HA6XA5SACFGVZJJR32N7JLHAVCNFSM6AAAAABWM422UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZSGA2DSNZQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jhuckaby]

Yeah, I think so? Something like this may work:

#!/bin/bash

echo "Launching at second 00..."
/usr/bin/your-script.sh &
sleep 10;

echo "Launching at second 10..."
/usr/bin/your-script.sh &
sleep 10;

echo "Launching at second 20..."
/usr/bin/your-script.sh &
sleep 10;

echo "Launching at second 30..."
/usr/bin/your-script.sh &
sleep 10;

echo "Launching at second 40..."
/usr/bin/your-script.sh &
sleep 10;

echo "Launching at second 50..."
/usr/bin/your-script.sh &
sleep 10;

The ampersands (&) after your launch commands should launch them in the background, allowing the overall script to continue.

[cjboat]

I’ll give that a go. Thank you!

…

On Mon, Feb 3, 2025 at 4:03 PM Joseph Huckaby ***@***.***> wrote: Yeah, I think so? Something like this may work: #!/bin/bash echo "Launching at second 00..." /usr/bin/your-script.sh & sleep 10; echo "Launching at second 10..." /usr/bin/your-script.sh & sleep 10; echo "Launching at second 20..." /usr/bin/your-script.sh & sleep 10; echo "Launching at second 30..." /usr/bin/your-script.sh & sleep 10; echo "Launching at second 40..." /usr/bin/your-script.sh & sleep 10; echo "Launching at second 50..." /usr/bin/your-script.sh & sleep 10; The ampersands (&) after your launch commands should launch them in the background, allowing the overall script to continue. — Reply to this email directly, view it on GitHub <#857 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA3VT5GLTIZUVXCBKVR2U2D2N7KTXAVCNFSM6AAAAABWM422UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZSGA3TANJYGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>