Re: some quotes about samba-vscan

Rainer Link <[email protected]> Wed, 23 Feb 2005 03:36:01 +0100
Newsgroups gmane.comp.security.virus.openantivirus.general
Message-ID <[email protected]>
On Tue, Feb 22, 2005 at 05:41:58PM +0100, jcuissinat wrote:
> the following messages :
> #################
> f?v 22 17:14:53 crible smbd_vscan-clamav[6810]: samba-vscan 
> (vscan-clamav 0.3.6RC1) connected (Samba 3.0), (c) by Rainer Link, 
> OpenAntiVirus.org
> f?v 22 17:14:53 crible smbd_vscan-clamav[6810]: INFO: connect to service 
> IPC$ by user xxxxxx

This is just normal logging by samba-vscan, which can not be switched
off. 

> f?v 22 17:14:53 crible smbd_vscan-clamav[6810]: [2005/02/22 17:14:53, 0] 
> clamav/vscan-clamav.c:vscan_connect(159)
> f?v 22 17:14:53 crible smbd_vscan-clamav[6810]:   configuration file is: 
> /etc/samba/vscan-clamav.conf
> #################


Looks like you're logging Samba via syslog. Actually, that's an
DEBUG(0, ...) statement in samba-vscan which needs to be changed

> In our test-school with a average of 60 connected people at the same 
> time (2000 students and more than 150 pc), our syslog file is know 
> unreadable !

What do you mean by unreadable? Too many samba-vscan related messages?
c'mon, it's Unix, so what about

# grep -iv smbd_vscan < /var/log/messages | less

> Is there a possibility to set file logging options more specifically ?
> In the same way, is it possible to define a specific file for virus 
> logging ?

Only syslog is supported. So, change include/vscan-global.h (the
SYSLOG_IORITY and SYSLOG_FACILITY setting) and your syslog.conf
accordingly. And don't forget to re-compile the vscan-clamav module.

best regards
Rainer Link





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click