Weirdnesses in McAfee autoupdate

Julian Field jkf at ecs.soton.ac.uk
Tue Jan 15 08:57:14 GMT 2002


At 22:26 14/01/2002, you wrote:
>On Mon, Jan 14, 2002 at 07:18:26PM +0000, Julian Field wrote:
> > At 16:50 14/01/2002, you wrote:
> > >I also experience this problem. The unlink and symlink does not appear
> to be
> > >working. I'm not sure that LockMcafee and UnlockMcafee are working either
> > >because I do not see the print statements when running autoupdate from the
> > >command line. Weird. It was working prior to upgrading from 2.62 to 3.00-3
> >
> > But I haven't touch the mcafee autoupdate script in months...
>
>revision 1.1
>date: 2001/12/13 18:25:07;  author: jkf;  state: Exp;
>branches:  1.1.2;
>Added McAfee autoupdate script with some bug-fixes from a user.
>
>
>That would I guess have first gone out in 3.0.

I stand corrected. I have changed the code back again (removed some
brackets from lines 115-116) and will put it in the next release.

The only interesting part of the diff was this:
114,115c115,116
< unlink $DATlink if -l $DATlink;
< symlink $DATdir, $DATlink;
---
 > unlink($DATlink) if -l $DATlink;
 > symlink($DATdir, $DATlink);

--
Julian Field                Teaching Systems Manager
jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
Tel. 023 8059 2817          University of Southampton
                             Southampton SO17 1BJ



More information about the MailScanner mailing list