ANNOUNCE: Version 3.22-5 released

[Julian Field]

At 13:26 23/07/2002, you wrote:
>Just installed ....
>I've upgraded my perl to 5.8.0 (All perl-tests are ok on my solaris8
>box...), but launching mailscanner, I got this warning:
>  "unix passed to setlogsock, but path not available at logger.pl line 44"
>
>Mailscanner now does not hang on this call, but changing the "unix" in
> >logger.pl:44  eval { Sys::Syslog::setlogsock('unix'); }; # Doesn't need
> syslogd -r
>to "inet" as follow
> >logger.pl:44  eval { Sys::Syslog::setlogsock('inet'); }; # Doesn't need
> syslogd -r
>the annoying warning disappear and the mailscanner logs goes to syslogd as
>usual (maybe slower than unix socket).
>
>Could be a good idea to set the logtype under mailscanner.conf in either
>unix/inet, maybe around the facility setting ???

The "unix" setlogsock works for nearly everyone, I think it's just a few
OS's where the "inet" is needed. The point of the exercise was to try to
*not* need anyone to edit their syslogd init.d script to edit the
command-line parameters to make inet work.
--
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