A |
artichoke |
Allow commented-out cron jobs.
Suppose we have a cron job that runs every 5 minutes.
*/5 * * * * /usr/local/bin/someprogram
We think this might be too often, so we replicate this line a few times, edit it, and comment out all but one.
# */5 * * * * /usr/local/bin/someprogram
15 0,12 * * * * /usr/local/bin/someprogram
# 15 0,8,16 * * * /usr/local/bin/someprogram
# 15 7 * * * /usr/local/bin/someprogram
Now we can uncomment any one of these lines at a time, while we are looking for the right frequency for this job.
Unfortunately, as soon as we make any change from DirectAdmin's cron jobs screen, all the commented-out lines get deleted. This is loss of data.
As mentioned in a couple of other feature requests,[1],[2] comments should generally be permitted and preserved.
[1] feedback.directadmin.com/b/feature-requests/allow-arbitrary-private-comments-almost-everywhere/
[2] feedback.directadmin.com/b/feature-requests/allow-and-preserve-dns-comments/
Activity Newest / Oldest
flexjoly
this is really needed!!
At the moment to disable a cron job, we set it on a different month, so it does not run at this moment.
Also a private-comment is really needed. For one client we have 2 double cron jobs with different time-settings. Because there is no comment, I do not know why we did it this way