From 69d69e2cb898f77827d2cf2c06a7f6fcd5157567 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Sun, 11 Jul 2010 23:20:15 +0200 Subject: crond: mention other cronds' behavior in comment. no code changes Signed-off-by: Denys Vlasenko --- miscutils/crond.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'miscutils/crond.c') diff --git a/miscutils/crond.c b/miscutils/crond.c index a459c6a8c..66110bb85 100644 --- a/miscutils/crond.c +++ b/miscutils/crond.c @@ -304,13 +304,15 @@ static void FixDayDow(CronLine *line) //if crontab was reloaded: crond thinks that "new" job is different from "old" //even if they are in fact completely the same. Example //Crontab was: -// 0-59 * * * job1 -// 0-59 * * * long_running_job2 +// 0-59 * * * * job1 +// 0-59 * * * * long_running_job2 //User edits crontab to: -// 0-59 * * * job1_updated -// 0-59 * * * long_running_job2 +// 0-59 * * * * job1_updated +// 0-59 * * * * long_running_job2 //Bug: crond can now start another long_running_job2 even if old one //is still running. +//OTOH most other versions of cron do not wait for job termination anyway, +//they end up with multiple copies of jobs if they don't terminate soon enough. static void delete_cronfile(const char *userName) { CronFile **pfile = &G.cron_files; -- cgit v1.2.3