Hello. This is good info to know, but I think in this instance the standard script is fine for my needs. The antivir program sends an email of its own when it does the update, and this already contains the status. For me, I'm OK just having that message. Of course, if I wanted it done just through cron, I could turn off the antivir message from its .conf file, and implement this change. It would be perfect for that. Sorry I have to use Outlook. Until I get Evolution 2 installed and talking to our Exchange servers, I'm stuck :-( Bye for now, Stuart. -----Original Message----- From: Carlos E. R. [mailto:robin1.listas@tiscali.es] Sent: Friday, October 08, 2004 3:06 PM To: SuSE Linux English Subject: RE: [SLE] Updating antivir via cron results in failure The Friday 2004-10-08 at 10:55 -0400, Powell, Stuart wrote: Mmm. Your mail program has a problem: it is not keeping threading information, and thus, your post doesn't appear to be an answer to my previous post. I almost did not see it.
I checked into the README as suggested the other day, and it looks like the answer to this is indeed right there. My antivir_update script works OK, but does not include any checking for the return code. The README has an example of what I should be using, but I'd like confirmation of the logic.
I think it is correct. Perhaps you want to change a litle thing so that it outputs 1 when there was a problem: ;; *) echo "AntiVir had an error trying to update" exit 1 ;; esac