On Fri, 29 Jul 2005 at 23:17:22 +1000, Kevin O'C wrote: > > yes, my polish friend, i did not expect such a > prestigious reply. some study is in order. > while you're posting, can you offer something to solve > this problem? > > :-> Sysadmin GSoWat Melbourne Australia
I'm not familiar with possible 'xmessage' problems, but I managed to use a few commands for testing, like 'date', 'echo', 'logger'. One condition that has to be fulfilled to have VirusEvent working is *using full pathnames* both to commands and to filenames for output (in case you want to do output directly to files). But, as you already wrote, you used "VirusEvent /whatever/whatever/xmessage "virus found"" where "/whatever/whatever/xmessage" I understand as the full pathname to 'xmessage', so I don't know why it didn't work for you. Provided that you really run clamd as root (not a very good idea, BTW) and that there were no problems with accessing the files for scanning. Here you are an example which worked for me: VirusEvent /usr/bin/logger "Test. Name: %v has been found." which gave in the user.log: Jul 29 16:37:41 hostname logger: Test. Name: Eicar-Test-Signature has been found. -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only tomek at lodz.tpsa.pl http://www.lodz.tpsa.pl/iso/ | ones and zeros. tomek at clamav.net http://www.ClamAV.net/ A GPL virus scanner _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
