Autoupdate cron jobs (sophos)

[Mike Dunderdale]

Rather than have a cron job to update the virus identities

I simply have an alias that runs the update whenever an alert is sent out
by Sophos:

(alias file)

--------------------------------
sophos_ide:"|/path_to_scripts/update_sophos_ide.sh"
--------------------------------

and the file update_sophos_ide.sh :

---------------------------------
#!/bin/sh
PATH=/usr/bin:/usr/local/bin ; export PATH
/opt/Sophos/bin/autoupdate >> /log_path/update_sophos_ide.log 2>1
----------------------------------

There shouldn't be anything in the update_sophos_ide.log, but the
autoupdate script for sophos will put a record in the syslog.

Shouldn't really be too much hassle to do this for another virus update
program.

Simply subscribe the alias to the virus/update alert mailing list, and
bob's yer uncle.

M.

On Fri, 6 Dec 2002, Peter Nitschke wrote:

> As an aside, is once a day enough these days?
>
> I was lucky with Klez, my daily cron updated F-prot between when they
> released the update and when it first hit here.  But one of my clients got
> hit from another email account even though he has a 24/7 connect and
> Nortons updating every 4 hours.
>
> At that point, I decided to run the update every hour and feel much
> happier.
>
> Peter
>
>
>
>
> *********** REPLY SEPARATOR  ***********
>
> On 5/12/2002 at 12:28 PM Dawes, Stephen wrote:
>
> >Perhaps the way to go is:
> >1. to take your suggestion #1, a script for each of the supported AV
> >scanners.
> >2. keep them in, hmmm I don't know, AVUpdates directory in the
> >MailScanner tree.
> >3. Move the appropriate auto update scripts into cron.daily, based on
> >the AV scanners that are identified in MailScanner.conf as part of the
> >start process for MailScanner. This would, of course, run each time you
> >start MailScanner.
> >The advantage to my idea, is that then the MailScanner user identifies
> >their AV application to MailScanner in one place and the application
> >takes care of the rest, as is the intention, or at least that is how I
> >am perceiving it. Better yet, have a script called something like
> >MailScanner-AV-Update that is placed in cron.daily that reads
> >MailScanner.conf to see which of the auto update scripts it needs to
> >run, and then it runs them.
> >
>

-------------------------------------------------------------------------
           Mike Dunderdale                |  tel: ++44 20 7679 2756
IT Systems Manager, Geomatic Engineering  |  fax: ++44 20 7380 0453
     mike.dunderdale at ge.ucl.ac.uk         |  mob: ++44 7939 455 245