On 2016-03-05 20:44:33 [+0100], Christian Pernegger wrote: > Thank you for getting back to me on this. > > Yes, cron.weekly seems to run at 6:47 and the freshclam update every > other hour at :46 ...
every other? I assumed twice a day. Probably got the numbers wrong. Btw: is this the cron/ anacron package or systemd's cron stuff? > I'll try the delaycompress option. Do you know if there's anything I > can do to fix the root cause, i.e. the two cron jobs running so close > together? It's a server that runs 24/7, there's plenty of time for > them to get out of each other's hair. I don't know if this is the cron daemon optimizing things or if it is really by chance that cron.weekly runs at :47 while debconf decided :46 is a good one. When you select `cron' in debconf then it will roll the big dice and come up with a number between 0 and 59 for the minute value. hour is just 24/x depending on the interval you select. It seems you had bad luck and those two came close together. So either you edit it manually (/etc/cron.d/freshclam or so) or try again your luck with debconf. Assuming the minute value gets set to :15 and then out of the sudden cron.weekly runs at 6:15 then it might be optimizing on cron's side (but then this is the first report). So there is this. I don't know how easy it would be to get both sides using `flock' so they don't try writting to the same file at the same time. And we have multiple scenarios like daemon mode, cron mode and so on. So *I* really think just adding the extra option to lograte is the simplest thing to do. > > Christian Sebastian _______________________________________________ Pkg-clamav-devel mailing list Pkg-clamav-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel