Hi;
I've seen this as well. I did a cpan upgrade and upgraded all perl
mods on a BSD, but not SA which was at 3.2.3. I think that may be due to
an issue with Sys:Syslog v0.20
SA seems to be working fine, as you say.
[96054] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains:
/usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/BSDPAN
/usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl
/usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval 14)
line 2.
[96054] error: BEGIN failed--compilation aborted at (eval 14) line 2.
rgds
n
Jonathan Armitage wrote:
> Apologies if I am asking in the wrong place, since I can see that
> there are several possible reasons.
>
> We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box
> running Red Hat 9. At the same time I used CPAN to upgrade any
> out-of-date perl modules.
>
> Now, when SA starts, we get the following error:
>
> Starting SpamAssassin daemon...
> [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC
> contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux
> /usr/local/lib/perl5/site_perl/5.8.8
> /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8
> /usr/local/lib/perl5/site_perl) at (eval 11) line 2.
> [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2.
>
> done.
>
> The error comes up twice, but SA does in fact start, and appears to be
> functioning normally. Does anyone know why it suddenly wants to load a
> Win32 module?
>
> Jon
>
> Jon Armitage
> System Administrator, 365 Media Group
>
