-
Notifications
You must be signed in to change notification settings - Fork 78
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
Add option to validate crontab file #59
Comments
This is a good RFE proposal. If you want to work on a PR, please go ahead. |
fcappi
pushed a commit
to fcappi/cronie
that referenced
this issue
Jun 10, 2020
Closes cronie-crond#59 Signed-off-by: Fernando Cappi <[email protected]>
fcappi
pushed a commit
to fcappi/cronie
that referenced
this issue
Jun 10, 2020
Closes cronie-crond#59 Signed-off-by: Fernando Cappi <[email protected]>
t8m
pushed a commit
that referenced
this issue
Jun 11, 2020
* Add new option to test a crontab file syntax without installing it * Fix code style issues in crontab.c Closes #59 Signed-off-by: Fernando Cappi <[email protected]> Co-authored-by: Fernando Cappi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys,
I would like to propose the addition of a new option that would allow us to only validate the crontab file and do NOT update the user config.
This would be very helpful in scenarios where you want to validate the crontab before actually updating the user configuration.
Examples:
Since the edit option already validates the file, I think it should be an easy change to add this feature, cause the validation logic is already in place.
What do you guys think about that?
If you agree, I would be glad to help, making the changes and submit a PR.
Suggestion:
Thanks!
The text was updated successfully, but these errors were encountered: