Dear Harald, the first bug report states that crond is not launched as the last daemon, when sysv init is used.
If we start a new debian system now, all services to be started in /etc/rc*.d are prefixed with S01. For example, /etc/rc5.d/S01cron is used to launch crond, which will be run before other service occurring in alphanumeric order, like /etc/rc5.d/S01mariadb for instance. The package cron provides /etc/init.d/cron, and no post-installation process is provided to populate /etc/rc*.d directories, neither to reorganize them. So, I fear that the best solution to this particular issue, would be to rename manually the file /etc/rc5.d/S01cron to someting like /etc/rc5.d/S99cron yourself, or to find people wanting to maintain sysv init scripts, and able to implement your wishes. ---- In your second post to this same bug report, you noticed that --------------8<------------------------ I just had the case that cron ran a user's @reboot job, even though his $HOME wasn't mounted via NFS yet. init was systemd. --------------8<------------------------ The current version of cron provides the file cron-service which features this particular line for the boot sequence: After=remote-fs.target nss-user-lookup.target So, if systemd does its job properly, a home directory mounted via NFS is mounted *before* crond can make anything related to the home's owner. I close the bug report now. Feel free to reopen it if something is wrong. Best regards, Georges. -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: PGP signature
