On Sun, Jan 13, 2008 at 11:49:57AM +0100, Axel Beckert wrote: > At least since updating to this version of cron on kfreebsd-amd64 (maybe > earlier), cron seems to look for the pid in /etc/crond.pid which > doesn't work. It argues about it as follows:
Ummm... there are several issues here, you should report them separately: > a) The usage of /etc/crond.pid violates the FHS and therefore the Debian > Policy Manual, section 9.1.1 Your architecture's /usr/include/paths.h (this is provided by the libc6-dev) header is missing the following line: #define _PATH_VARRUN "/var/run/" This makes cron use /etc/ instead of /var/run. > b) The init.d script is unable to stop or restart crond. Yes, that's because the pid file is not found. > c) The init.d script does not return an exit code unequal to zero if it > fails (see the prompts above). Init.d scripts which fail to stop should still return a code equal to zero (see the LSB specs). I don't parse your command lines, could you explain how can I infer that the exit code is not cero? Regards Javier
signature.asc
Description: Digital signature
