Red Hat Bugzilla – Bug 5462
sysklogd didn't allow remote logging..it said setsockopt(BSDCOMPAT), suspending inet
Last modified: 2014-03-16 22:10:08 EDT
running sysklogd -r fails saying setsockopt(BSDCOMPAT),
sorry for the short problem report. but the porblem is
short, this modfication
is done on the sysklogd-fixDoS.patch
This is fixed in the latest sysklogd package (1.3.31-12.)
*** Bug 5471 has been marked as a duplicate of this bug. ***
Two RH6.0 machines seem to have no remote syslog after
sysklogd-1.3.31-11.i386.rpm. Downgrading to
fixes remote reception.
I upgraded because I'm having problems with syslog/klog
getting in a bad state while remotely logging a sonicwall
This "bad state" causes login to hang, apparently waiting on
klogd. If I
(re)start klogd (sometimes it's already dead), the login
machine is also logging 4 jetdirect boxes. During this bad
The other RH6.0 machine is logging only one jetdirect box
shown this problem.
I enable remote reception by adding the "-r" switch to the
# See how we were called.
case "$1" in
echo -n "Starting system logger: "
# we don't want the MARK ticks
daemon syslogd -r -m 0
echo -n "Starting kernel logger: "