Autoupdate cron jobs

[Dawes, Stephen]

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. 




Stephen Dawes  <B.A., B.Sc.>
The City of Calgary                   |  Phone: (403) 268-5527
   Web Business Office #8300          |  Fax:   (403) 268-6423
   PO Box 2100 Postal Station M.      |  Email: Stephen.Dawes at calgary.ca
   Calgary, Alberta, Canada. T2P 2M5  |  Web:  http://www.calgary.ca

FOIPP NOTIFICATION
This communication is intended ONLY for the use of the person or entity 
named above and may contain information that is confidential or legally 
privileged. If you are not the intended recipient named above or a
person
responsible for delivering messages or communications to the intended 
recipient, YOU ARE  HEREBY NOTIFIED that any use, distribution, or 
copying of this communication or any of the information contained in it 
is strictly prohibited. If you have received this communication in
error,
please notify us immediately by telephone and then destroy or delete
this
communication, or return it to us by mail if requested by us.

Thank you for your attention and co-operation. 




> -----Original Message-----
> From: Julian Field [mailto:mailscanner at ECS.SOTON.AC.UK]
> Sent: 2002 December 05 11:14 AM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Autoupdate cron jobs
> 
> 
> At 18:04 05/12/2002, you wrote:
> > > At 16:17 05/12/2002, you wrote:
> > >>On Thu, 5 Dec 2002 10:25:51 -0500 Gerry Doris 
> <gerry at dorfam.ca> wrote:
> > >> > The only minor problem I have is that I always forget 
> to remove the
> > >> Sophos entry in cron.daily since I only run F-Prot.
> > >>
> > >>I also don't like it. Maybe it's better to use another rpm
> > >>(antivirus-update-scripts.rpm)
> > >>for that?
> > >
> > > The first thing the Sophos cron script does is check that 
> Sophos is
> > > actually installed. It exits immediately if it isn't installed. So
> > > what's wrong with just leaving it there? I can't see it 
> does any harm. I
> > > agree it wastes about a millisecond of CPU once per day, 
> but that's
> > > hardly the end of the world.
> > > --
> > > Julian Field
> > > www.MailScanner.info
> > > MailScanner thanks transtec Computers for their support
> >
> >Well, for me it's definitely NOT the end of the world.  It 
> just generates
> >an error message in my logs.  I just remove the file and 
> forget about it.
> 
> What I am tempted to do is add more of them (one for each of 
> the autoupdate
> scripts).
> Would you all prefer
>     1) one for each autoupdate script,
> or
>     2) 1 that did the autoupdate script for all of the 
> scanners it can find
> installed
> or
>     3) 1 sample script that you can edit for your scanner 
> (i.e. what you
> get now)
> ??
> 
> Option 1 would create much simpler scripts, which people will 
> find easier
> to edit if they have their virus scanner installed in a non-standard
> location. People are far more reluctant to edit a big script 
> than a little
> simple one.
> --
> Julian Field
> www.MailScanner.info
> MailScanner thanks transtec Computers for their support
>