On Sat, 8 May 2004, Per-Olov Sj�holm wrote:

> I want to point out that I have not yet looked through the source code.

You should... that's where all the documentation is.  ;)

> But I do think that it would be nice to include how the clamd log to
> syslog to the manpage for clamd. It is clear that we can log to syslog by
> adding "LogSyslog" to clamav.conf. It is also easy to see that it log to
> syslog by adding "*.* /var/log/logfilename" to syslog.conf. But it would
> be more nice to be able to sort the clamd entries by knowing how it logs.
>
> Will it log to mail.info ? local"n".info ? Or What ?

clamd and freshclam log to local6.*
clamav-milter logs to mail.*.

It'd be nice if the local6.* could be user-defined at runtime.  It was a
bit of a hassle here since we were using local6 for something else
already.

Damian Menscher
-- 
-=#| Physics Grad Student & SysAdmin @ U Illinois Urbana-Champaign |#=-
-=#| 488 LLP, 1110 W. Green St, Urbana, IL 61801 Ofc:(217)333-0038 |#=-
-=#| <[EMAIL PROTECTED]> www.uiuc.edu/~menscher/ Fax:(217)333-9819 |#=-
-=#| The above opinions are not necessarily those of my employers: |#=-
-=#| UIUC CITES Security Group || Beckman Imaging Technology Group |#=-


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to