On Mon 31 Mar 2014 at 13:22:04 +0300, David Baron wrote: > More ...
In another mail you were asked a single question. Do you have a response to that question? In the same mail an observation was made. It implied that the file cron-spamassassin-rules was put in /etc/cron.daily by you and not by a Debian package. Do you have a response to that too? We are now reduced to guessing that cron-spamassassin-rules is not a Debian file and it is the problem. > There is a locate script in /etc/cron.daily which should be run as a matter > or > daily anacron course. Has not been. No entry in syslog. Syslog has not been > daily-logrotated during this period either. There is an *mlocate* script in /etc/cron.daily. 1. Delete /var/spool/anacron.daily. 2. Move all the files out of /etc/cron.daily apart from 0anacron and mlocate. 3. Run '/usr/sbin/anacron -s'. 4. Does 'ps ax | grep cron' have '/usr/sbin/anacron -s' in its output and does syslog report that anacron was started? 5. 5 minutes later does /var/spool/anacron.daily exist and has syslog been updated to reflect that? Has '/usr/sbin/anacron -s' disappeared from the output of 'ps ax'? 6. Rename cron-spamassassin-rules to spamassassin-rules and add it to /etc/cron.daily. Repeat 1-5. An additional question: are the time data for /var/lib/mlocate/mlocate.db altered? 7. Kill any unwanted processes and repeat 1-6 after renaming spamassassin-rules to cron-spamassassin-rules. > The working part of the locate script can be run manually. > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140331123722.gh3...@copernicus.demon.co.uk
