Hello
I do
freshclam --quiet -l /var/log/clam-update.log
And I have this error :
ERROR: Can’t open /var/log/clam-update.log in append mode.
ERROR: Problem with internal logger.
Any idea ?
Thanks
Hello
I do
And I have this error :
ERROR: Can’t open /var/log/clam-update.log in append mode.
ERROR: Problem with internal logger.
Any idea ?
Thanks
Does that /var/log/clam-update.log file exist? Is it writable by the clamd user?
Yes it is there and it is writable
Hello,
I have had the same problem. It is writeable and it is there and owned by clamav. It should work this is the only box I had this problem on. Of course I installed qmail on the other boxes. Any other ideas? Funny I googled my question and it sent me here!
B
Yep funny.
Do you have an interworx box ?
I still have the pbm so if somebody know :-p
Pascal
Interworx Fedora Core 2
Yes I have an interworx box with fedora core 2. Someone in another forum suggested it was the config file being different then the command. I checked that and it did not make a difference. Maybe we are missing a package/rpm? Help please!
I’d do the following (as root):
chmod 751 /var/log
touch /var/log/clam-update.log
chown root.<clam user> /var/log/clam-update.log
chmod 660 /var/log/clam-update.log
Chris
H?h? Chris your the best
It uses to work
I’m Waiting for the cron job this night just to confirm that all is fine (as I do not remember if I had this error by launching this cmd directly)
:-p
Another quick question :
Now I can’t access directly to cmd in /sbin/xxx ou /usr/sbin
Do i miss something ?
For example for iptables I have to write the full link /sbin/iptables same for others as hwclock or etc…
My server was reboot few days ago
Do I have to change the $PATH ? don’t remember how ?
Thanks again
Pascal
Another quick question :
Now I can’t access directly to cmd in /sbin/xxx ou /usr/sbin
Do i miss something ?
For example for iptables I have to write the full link /sbin/iptables same for others as hwclock or etc…
My server was reboot few days ago
Do I have to change the $PATH ? don’t remember how ?
What user are you when doing so? root? Make sure when you ‘su’ to root that you include the “-” arg:
i.e.
su - root
Chris
erfff some times I lost my brain :mad:
of course I have to use -
grrrrr squalito
Thanks again
Thank you
That worked perfectly. Thank you