syslog not defined?
Tim Tyler
tyler at beloit.edu
Thu Sep 19 16:01:07 IST 2002
Julian,
No, unfortunately, it is not running. I am assuming that it is crashing
because of the syslog error. Is it possible it might be crashing for some
other reason? Unfortunately, I am not getting anything logged to the syslog
for it so I can't get a hint. Is there a debug mode to run mailscanner that
might give me more information when trying to start up?
Is there a trick to get it to avoid the syslog issue? This is a bit
strange since 2.6 never gave me errors.
Tim
>
>Can you check that, after it printed this error, MailScanner isn't actually
>running? MailScanner now tries to start the syslogging without needing a
>UDP socket open to your syslogd, but backs off and tries the old way if
>that failed. So it's quite possible that this error is harmless and
>MailScanner is still running after it prints this error.
>
>At 21:13 18/09/2002, you wrote:
>>Mailscanner,
>> I tried to upgrade from mailscanner 2.6 to 3.22.14 but I got this error
>>when starting it up:
>>
>># /var/spool/mailscanner/bin/check_mailscanner
>>Starting virus scanner...
>>Your vendor has not defined the Sys::Syslog macro _PATH_LOG at
>>/usr/local/lib/perl5/5.6.0/aix/Sys/Syslog.pm line 277.
>>
>>I am running AIX4.3.3.
>>
>>Any suggestions for resolving this? Note: I didn't get this error with 2.6.
>>
>>--
>>Tim Tyler
>>Network Manager - Beloit College
>>tyler at beloit.edu
>
>--
>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
>
--
Tim Tyler
Network Manager - Beloit College
tyler at beloit.edu
More information about the MailScanner
mailing list