On Sunday 27 November 2005 6:35 pm, Randall R Schulz wrote: Randall,
Thus Scott's criteria say, to take the cron.hourly case as an example, the file's change time is either less than 60 or greater than 60 minutes, but not "exactly" 60 (whatever "exactly" means to find, as I mention above).
It seems unlikely this is really what you intended, but I don't really know that, do I?
I can't speak to the interpretation of what is really going on, but I will comment that the non-minus sign version is the one that the May thread here agreed was the fix for the problem with run-crons. http://lists.suse.com/archive/suse-linux-e/2005-May/1473.html All I know is that I made that fix, without any minus signs, and cron.daily and cron.weekly are running correctly here and have been since May (course, this is a desktop that stays on 24/7 so that may make a difference). Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.9-default x86_64 SuSE Linux 9.3 (x86-64)