|Main Archive Page > Month Archives > spamassassin-dev archives|
--- Comment #12 from Mark Martinec <Mark.Martinec@ijs.si> 2011-09-08 00:49:42 UTC ---
> Any updates on this matter ?
> # perl -le 'use Sys::Syslog; print Sys::Syslog->VERSION'
> I upgraded Perl to 5.14.1, rsyslog, etc... got the latest SVN, etc...
> still the same.
So far it seems you are the only one experiencing this problem.
Troubleshooting it without being able to reproduce it is difficult.
I'm also running Perl 5.14.1 (*not* multithreaded) with Sys::Syslog 0.29,
and it works fine.
Did the self-test of a module Sys::Syslog run without errors?
# make test
PERL_DL_NONLAZY=1 /usr/local/bin/perl5.14.1 "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00-load.t .......... 1/1 # Testing Sys::Syslog 0.29, Perl 5.014001,
t/00-load.t .......... ok
t/constants.t ........ ok
t/data-validation.t .. skipped: POE is not available
t/distchk.t .......... ok
t/pod.t .............. ok
t/podcover.t ......... ok
t/podspell.t ......... skipped: Pod spelling: for maintainer only
t/portfs.t ........... ok
t/syslog.t ........... ok
All tests successful.
Files=9, Tests=319, 1 wallclock secs ( 0.05 usr 0.06 sys + 0.65 cusr 0.15
csys = 0.91 CPU)
The test sends log messages to a facility local0.
Check that these test log messages in a log file look alright.
You may need to adjust /etc/syslog.conf to see them.
Moreover, you may try experimenting with an option --syslog-socket
of spamd. Its man page has this to say:
Specify how spamd should send messages to syslogd. The type can be
any of the socket types or logging mechanisms as accepted by the
subroutine Sys::Syslog::setlogsock(). Depending on a version of
Sys::Syslog and on the underlying operating system, one of the
following values (or their subset) can be used: "native",
"eventlog", "tcp", "udp", "inet", "unix", "stream", "pipe", or
"console". The value "eventlog" is specific to Win32 events logger
and requires a perl module Win32::EventLog to be installed. For
more information please consult the Sys::Syslog documentation.
A historical setting --syslog-socket=none is mapped to
A default for Windows platforms is "none", otherwise the default is
to try "unix" first, falling back to "inet" if perl detects errors
in its "unix" support.
Some platforms, or versions of perl, are shipped with old or
dysfunctional versions of the Sys::Syslog module which do not
support some socket types, so you may need to set this option
explicitly. If you get error messages regarding __PATH_LOG or
similar spamd, try changing this setting.
The socket types "file" is used internally and should not be
specified. Use the "-s" switch instead.
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.