I'm running FC2, I want my system to accept remote log messages.

I've set this option on my /etc/sysconfig/syslog
# Options to syslogd
# -m 0 disables 'MARK' messages.
# -r enables logging from remote machines
# -x disables DNS lookups on messages recieved with -r
# See syslogd(8) for more details
SYSLOGD_OPTIONS="-m 0"

# Add option to accept remote syslog messages
SYSLOGD_OPTIONS="${SYSLOGD_OPTIONS} -r"

# Options to klogd
# -2 prints all kernel oops messages twice; once for klogd to decode, and
# once for processing with 'ksymoops'
# -x disables all klogd processing of oops messages entirely
# See klogd(8) for more details
KLOGD_OPTIONS="-x"

and restarted syslog then in /var/log/messages I came to found the syslog has shutted down again. Following was the message

Aug 2 10:34:36 p15187670 kernel: Kernel logging (proc) stopped.
Aug 2 10:34:36 p15187670 kernel: Kernel log daemon terminating.
Aug 2 10:34:37 p15187670 syslog: klogd shutdown succeeded
Aug 2 10:34:37 p15187670 exiting on signal 15
Aug 2 10:34:37 p15187670 syslogd 1.4.1: restart (remote reception).
Aug 2 10:34:37 p15187670 syslog: syslogd startup succeeded
Aug 2 10:34:37 p15187670 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 2 10:34:37 p15187670 kernel: process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
Aug 2 10:34:37 p15187670 syslog: klogd startup succeeded
Aug 2 10:34:37 p15187670 syslog: syslogd shutdown succeeded
Aug 2 10:34:37 p15187670 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 2 10:34:37 p15187670 kernel: process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
Aug 2 10:34:37 p15187670 syslog: klogd startup succeeded
Aug 2 10:34:37 p15187670 syslog: syslogd shutdown succeeded


Can anyone tell me what the problem and how can i make syslog to accept remote messages.

Regards,
Imran

kernel: process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
The syslog package wasn't updated to kernel 2.6 specs. The message however is just of "informational" level and shouldn't make syslogd exit, /etc/sysconfig/syslog looks OK for receiving remote messages and the options shouldn't make syslogd exit either. Check if there's a syslog package update or else try if syslog-ng works for you.