well, for anything I put in crontab, I have to put >/dev/null 2>&1 at
the end of it to catch the output. the 2>&1 has to do with the process
going into the background instead of running in the foreground (I
think).
Although I've always been of the opinion that it's the user's
responsibility to ensure they don't get or send viruses, not the network
admin's. If they're too stupid to be running a recent virus scanner,
they deserve what they get.
> -----Original Message-----
> From: exim-users-admin@???
> [mailto:exim-users-admin@exim.org] On Behalf Of Angel Marin
> Sent: Sunday, June 16, 2002 3:45 AM
> To: Tom Kistner
> Cc: exim-users@???
> Subject: RE: [Exim] Exiscan and Clam Antivirus (SOLVED)
>
>
> I had the same issue when I used the local_interfaces conf
> setting of exim. With exim + exiscan-4.04-7 + Mcafee
> viruscan. If I comment the local_interfaces setting all works well :?
>
> With exiscan-4.05-8 is working well w/wo local_interfaces setting.
>
> Angel.
>
> > -----Mensaje original-----
> > On Tue, Jun 04, 2002 at 02:37:13PM -0300, Patrick Boutilier
> > (boutilpj@???) wrote:
> >
> > > Now it works in the background as well. Any reason why
> the 2>&1 is
> > > where it is?
> >
> > Looks like it is in the wrong spot. I corrected this in
> > exiscan-4.04-8. I have no idea why the problem only showed up with
> > that particular scanner.
> >
> > Thanks for the report :)
> >
> > /tom
>
>
> --
>
> ## List details at
> http://www.exim.org/mailman/listinfo/exim-> users Exim details
> at http://www.exim.org/ ##
>
>
>
