Skip to main content
Homepage
Explore
Search or go to…
/
Sign in
Explore
Primary navigation
Project
C
chkcrontab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Collapse sidebar
Snippets
Groups
Projects
Show more breadcrumbs
Kevin Lyda
chkcrontab
Commits
b92e6c9c
Commit
b92e6c9c
authored
May 26, 2012
by
Kevin Lyda
Browse files
Options
Downloads
Patches
Plain Diff
Marked up README.
Now using reStructuredText. Cleaned up a few text errors. Added link to travis test status.
parent
bdee3281
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.rst
+34
-0
34 additions, 0 deletions
README.rst
with
34 additions
and
0 deletions
README
→
README
.rst
+
34
−
0
View file @
b92e6c9c
Crontab linter.
==========
chkcrontab
==========
.. image:: https://secure.travis-ci.org/lyda/chkcrontab.png
:target: https://secure.travis-ci.org/lyda/chkcrontab
:alt: Build status
Crontab linter
==============
chkcrontab is a script to check crontab files like those in
chkcrontab is a script to check crontab files like those in
/etc/cron.d and /etc/crontab. It tries to catch glaring
errors
``
/etc/cron.d
``
and
``
/etc/crontab
``
. It tries to catch glaring
and warn on suspect lines in a crontab file. Some valid
lines
errors
and warn on suspect lines in a crontab file. Some valid
will generate warnings. Certain silly yet valid crontab lines
lines
will generate warnings. Certain silly yet valid crontab lines
will generate errors as well.
will generate errors as well.
Run this by doing ./chkcrontab crontab_file
Run this by doing::
chkcrontab crontab_file
Errors will cause a non-zero exit code. Warnings alone will not.
Errors will cause a non-zero exit code. Warnings alone will not.
To see sample output for a bad crontab, run the following:
To see sample output for a bad crontab, run the following:
:
./chkcrontab ./tests/test_crontab
./chkcrontab ./tests/test_crontab
See the ./tests/test_crontab.disable crontab for how to disable
See the
``
./tests/test_crontab.disable
``
crontab for how to disable
warnings and errors.
warnings and errors.
CONTRIBUTIONS
Contributions
=============
Please add unit tests for new features or bug fixes. To run all
Please add unit tests for new features or bug fixes. To run all
the unitests run ./setup test.
the unit
t
ests run
``
./setup test
``
.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment