> Try using LogFileUnlock, and checking the permissions on the device.
I suppose you mean putting
LogFileUnlock
in clamav.conf...
but it didn't help. Same error.
> Those do look like clam error messages. And no need to stick to stdout
> - stderr should work the same.
permissions on the devices:
# ll /dev/std*
lrwxrwxrwx 1 root root 4 Jan 23 2003 /dev/stderr -> fd/2
lrwxrwxrwx 1 root root 4 Jan 23 2003 /dev/stdin -> fd/0
lrwxrwxrwx 1 root root 4 Jan 23 2003 /dev/stdout -> fd/1
I guess anyone may write to fd/2, but it seems it (Linus Torvalds creation
version 2.4) don't want to open those in append mode...
Jeremy, how did you get this working !?
-ace
ps system is debian woody.
--
I wanna be the squeezer, and not the squeezie,
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
