virex cron

[lists3-200402]

Stroller <MacMonster at myrealbox.com> wrote:

>On Mar 27, 2004, at 10:05 pm, lists3-200402 wrote:
>
>>  does anyone know how to append a date to a summary for a virex cron
>>  job?... i checked the virex 7.2.1 manual and it doesn't seem to have a
>>  switch for that. here's my command:
>>
>  > /usr/local/vscanx/vscanx --move /SERVER/VOLUME/VIREX_OUT/QUARANTINE
>>  /SERVER/VOLUME/SHARE --recursive --unzip --atime-preserve
>>  --ignore-links  --summary >> /SERVER/VOLUME/VIREX_OUT/SUMMARY.TXT
>
>I think this should do it:
>    /usr/local/vscanx/vscanx --move /SERVER/VOLUME/VIREX_OUT/QUARANTINE
>/SERVER/VOLUME/SHARE --recursive --unzip --atime-preserve
>--ignore-links  --summary >> /SERVER/VOLUME/VIREX_OUT/SUMMARY.TXT &&
>echo "Finished at:"  >> /SERVER/VOLUME/VIREX_OUT/SUMMARY.TXT && date >>
>/SERVER/VOLUME/VIREX_OUT/SUMMARY.TXT
>
>For the hard-of-wrapping, that's all one line. The "&&" means "wait
>until the previous command is finished and then run the command that
>follows". I would personally prepend the date to the file, but you pays
>your money & takes your choice.
>
>Stroller.

wow, dude, you rock! here's the output (of course i've scanned a few 
times so there are no viruses):

	Summary report on /SERVER/VOLUME/*
	File(s)
        	Total files: ...........  126831
        	Clean: .................  126831
        	Not scanned: ...........       0
        	Possibly Infected: .....       4
        	Moved: .................       4
	Finished at:
	Sun Mar 28 08:35:23 EST 2004

(note: the four files that were found to be "possibly infected" and 
therefore "moved" are test files...see <http://eicar.com> for more 
info...the virex manual goes into more detail...pretty nifty)

the only problem i noticed is that now i get this error in the 
terminal when i run the cron script manually (cut/paste into root 
terminal):

	/SERVER/VOLUME/VIREX_OUT/QUARANTINE
         file could not be opened.

...the QUARANTINE folder's permissions were adjusted to this after i 
first saw the message:

	chown -R myself:admin /SERVER/VOLUME/VIREX_OUT

and then...

	chmod -R 777 /SERVER/VOLUME/VIREX_OUT/

...but i still got the same error. the report is fine (thanks a 
million, stroller!!!). should i disregard?

don