Did you edit your crontab using 'crontab -e'? If not, the cron daemon
probably won't reread the file on disk and is still acting upon the old
crontab.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Green
Sent: Monday, November 29, 2004
David Green wanted us to know:
>Subject: Cron <[EMAIL PROTECTED]> /usr/local/bin/freshclam --quiet
Maybe it's setup in a user crontab:
su - pop3
crontab -l
--
Regards... Todd
We should not be building surveillance technology into standards.
Law enforcement was not supposed to
On Mon, 2004-11-29 at 15:19 -0600, David Green wrote:
> Subject: Cron <[EMAIL PROTECTED]> /usr/local/bin/freshclam --quiet
> --daemon-notify -l /var/log/clam-update.log
> shell-init: could not get current directory: getcwd: cannot access
> parent directories: Permission denied
> /bin/sh: line 1:
