Recently a user on one of our systems (linux Ubuntu, but any *nix would be the same) had a crontab file missing a terminating newline.
It is common for *nix configuration files to require that terminating newline, cron being no different. However, no warning is provided when adding a file with no newline, and the command is never executed.
So, two fixes identify themselves.
- Run a cron process to check for these files.
- Provide a friendlier front end to cron.
The second is what this question is about. Either something to check the syntax before entering the file, or to front the whole entry process, which is a bit arcane anyway.
For this particular machine a command-line tool would be needed, since it is located at a data centre, and an X environment is not installed.