-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Specifying cron for a scheduled task #366
Comments
Yes, the cron parser is currently very rudimentary and only supports single numbers... |
This is what I supposed. Did you schedule something for this very interesting feature? At least for a list of minutes in the hour. I would really appreciate defining a schedule for specific minutes in the hour 😉 |
For sure... This was simply a quick "first version" so next version will add some more modifiers... |
Any scheduled date for this next version? Any chance in the next few days/weeks? I am currently setting up a new deployment for several hundred of hosts and I would like to know if I install the current version of NSClient or I still wait... |
I would say it wont make the 0.5.1 version which will have a release candidate in the next few days (need to run some test to make sur the installer is correct). So possibly beta versions in maybe a month then releases in a month or so after that. However if there is something specific you need I might be convinced to do an exception and see if I can get it into 0.5.1 |
Thanks @mickem. My only request would be to use such syntax: |
This should work n the latest 0.5.1 build. |
I declared some NSCA checks in scheduled tasks and I trid to use the
cron
parameter but when I set a value like10,25,40,55 * * * *
thenscp test --validate
raise an exception for the Scheduler:It look like if the NSClient did not handled the 10,25,40,55 as the cron minute but as minute,hour,day,month ?
What is the expected syntax to run a command several times on every hour at different minutes? Anyway, is it possible ?
The text was updated successfully, but these errors were encountered: