Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 5462 - sysklogd didn't allow remote said setsockopt(BSDCOMPAT), suspending inet
Summary: sysklogd didn't allow remote said setsockopt(BSDCOMPAT), suspendi...
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: sysklogd
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
: 5471 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 1999-10-01 02:17 UTC by mbartsch
Modified: 2014-03-17 02:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-10-01 16:16:35 UTC

Attachments (Terms of Use)

Description mbartsch 1999-10-01 02:17:36 UTC
running sysklogd -r fails saying setsockopt(BSDCOMPAT),
suspending inet.

sorry for the short problem report. but the porblem is
short, this modfication
is done on the sysklogd-fixDoS.patch

Comment 1 Bill Nottingham 1999-10-01 16:16:59 UTC
This is fixed in the latest sysklogd package (1.3.31-12.)

Comment 2 Bill Nottingham 1999-10-01 22:33:59 UTC
*** Bug 5471 has been marked as a duplicate of this bug. ***

Two RH6.0 machines seem to have no remote syslog after
upgrading to
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
proceeds. This
machine is also logging 4 jetdirect boxes. During this bad
state, all
logging stops.

The other RH6.0 machine is logging only one jetdirect box
and hasn't
shown this problem.

I enable remote reception by adding the "-r" switch to the
command line
in /etc/rc.d/init.d/syslog.

# 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: "
    daemon klogd
    touch /var/lock/subsys/syslog

Note You need to log in before you can comment on or make changes to this bug.