On Wed, 12 Feb 2003, Rick Knight wrote:
> in the command so I tried it without root but with everything else and
> got the same error. I have created a work-around using "freshclam
> --stdout | logger -p local6.info" in my crontab and "local6.*
> /var/log/clam-update.log" in /etc/syslog.conf. It w
Thanks for the reply Josh,
I am working with root's crontab and , except for --daemon-notify it
looks very much like yours.
Any other suggestions?
Thanks again,
Rick Knight
([EMAIL PROTECTED])
[EMAIL PROTECTED] wrote:
On Wed, 12 Feb 2003, Rick Knight wrote:
Thanks Wash,
Just a thought.
On Wed, 12 Feb 2003, Rick Knight wrote:
> Thanks Wash,
>
> I made the changes you suggested in crontab, but it did not like "root"
> in the command so I tried it without root but with everything else and
> got the same error. I have created a work-around using "freshclam
> --stdout | logger -p loca
Thanks Wash,
I made the changes you suggested in crontab, but it did not like "root"
in the command so I tried it without root but with everything else and
got the same error. I have created a work-around using "freshclam
--stdout | logger -p local6.info" in my crontab and "local6.*
/var/log/c
* Rick Knight <[EMAIL PROTECTED]> [20030211 21:00]: wrote:
> Thanks again Wash,
>
> Cron entries (I run it twice a day)
>0 6 * * * /usr/local/bin/freshclam --quiet -l /var/log/clam-update.log
>0 18 * * * /usr/local/bin/freshclam --quiet -l /var/log/clam-update.log
I know I could be anal b
Thanks again Wash,
Cron entries (I run it twice a day)
0 6 * * * /usr/local/bin/freshclam --quiet -l /var/log/clam-update.log
0 18 * * * /usr/local/bin/freshclam --quiet -l /var/log/clam-update.log
Output of "ls -al /var/log/clam-update.log"
-rw-r--r--1 clamav clamav 0 Feb
Wash,
Oops, that was a typo in my message. The log file is
/var/log/clam-update.log and the cron job specifies /var/log/clam-update.log
Thanks,
Rick Knight
([EMAIL PROTECTED])
Odhiambo Washington wrote:
Take a second look at your cron and verify that it has the file named
/var/log/clam-update.l
Thanks for the reply Wash.
Yes, /var/log/clam-update.log is owned by clamav.clamav and has 0644
permissions. Freshclam is run by root's cron script. It also make no
difference whether I run it as a daemon (freshclam -d -c 2 -l
/var/log/clam-update.log) or as a cron job (freshclam --quiet -l
/
* Rick Knight <[EMAIL PROTECTED]> [20030211 01:12]: wrote:
> Last Friday morning I started getting this error from my freshclam cron
> job ...
>
> ERROR: LOGGER: Can't open file /var/log/clam-update to write.
> ERROR: Problem with internal logger.
>
> Clamd and clamscan work fine and freshclam w
Last Friday morning I started getting this error from my freshclam cron
job ...
ERROR: LOGGER: Can't open file /var/log/clam-update to write.
ERROR: Problem with internal logger.
Clamd and clamscan work fine and freshclam works without logging. I've
checked file permissions and everything looks
10 matches
Mail list logo
