https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25245 --- Comment #37 from David Cook <dcook@prosentient.com.au> --- (In reply to Martin Renvoize from comment #35)
I agree with Katrin here I think.. I would say it's clearer to have the default in the .daily file as it's intended to be run daily and for an admin to move it to .d if they are keen to specify an exact time.
I suppose so. I'm just thinking about out-of-the-box minimal installations. It's no drama for me to change a cronjob time, but I wonder a bit about many small scale sysadmins out there using Koha.
Also, as an aside, it is my understanding that these two schemes work in different ways.. cron.d runs more like the original cron and just 'does a thing at time X' where as cron.daily (and friends) uses anacron in the background and as such 'does thing some time after X, with random delay Y and retries if the server is down'.
anacron should never be installed on a server. It's really more suited to desktops and laptops. That said, /etc/crontab will use it if it's present and executable. I'm looking at a customized Debian 9 Jessie and I see anacron installed and executable, and I'm looking at a Ubuntu 18.04 Bionic and I see that anacron is not installed. Sure enough, the Debian Jessie appears to be a Desktop image, while the Ubuntu is a headless server image. I think that actually helps make my case a bit for not using /etc/cron.daily heh. But that's just my 2 cents. It's not a hill I want to die on by any means. Happy for it to go in /etc/cron.daily if everyone else does. -- You are receiving this mail because: You are watching all bug changes.