https://community.hpe.com/t5/operating-system-linux/weird-problem-w-syslogd/m-p/2759438#M1895 Michael,<BR /><BR />Don't know how much help this is going to be but this is the result I get from a Redhat 7.1 system running the same kernel:<BR /><BR />[root@mash init.d]# ./syslog status<BR />syslogd (pid 438) is running...<BR />klogd (pid 443) is running...<BR /><BR />[root@mash init.d]# syslogd -m 0<BR />syslogd: Already running.<BR />[root@mash init.d]# echo $?<BR />1<BR /><BR />So what I can say is this:<BR /><BR />run ps -aux | grep syslog, make sure there IS no process running (don't trust the script), if there is manually kill it.<BR /><BR />Look at the file /var/run/syslogd.pid and see which process id it thinks syslogd is running under.<BR /><BR />If syslogd happened to be running, then kill it, move the messages file across to messages.bak and touch the messages file (giving it the same permissions/owner as the original messages file). Then try restarting syslogd.<BR /><BR />Good luck,<BR /><BR />Shane.<BR /><BR /> Wed, 10 Jul 2002 05:55:57 GMT Shane Hjorth 2002-07-10T05:55:57Z https://community.hpe.com/t5/operating-system-linux/weird-problem-w-syslogd/m-p/2759437#M1894 All, syslogd is not logging. All my messages file is of zero length. When I restarted syslog manually; syslog failed to start, but if I do "./syslog status", it tells me that syslog is running. However, when I run the cmd manually "syslod -m 0" and "echo $?", it returns code "130", I believe it should be a return code of 0. Any one have any idea as to why syslogd is not behaving properly? BTW, this is on RH 7.1 running kernel version 2.4.2-2smp. Thanks. Mon, 08 Jul 2002 15:02:18 GMT https://community.hpe.com/t5/operating-system-linux/weird-problem-w-syslogd/m-p/2759437#M1894 K.C. Chan 2002-07-08T15:02:18Z https://community.hpe.com/t5/operating-system-linux/weird-problem-w-syslogd/m-p/2759438#M1895 Michael,<BR /><BR />Don't know how much help this is going to be but this is the result I get from a Redhat 7.1 system running the same kernel:<BR /><BR />[root@mash init.d]# ./syslog status<BR />syslogd (pid 438) is running...<BR />klogd (pid 443) is running...<BR /><BR />[root@mash init.d]# syslogd -m 0<BR />syslogd: Already running.<BR />[root@mash init.d]# echo $?<BR />1<BR /><BR />So what I can say is this:<BR /><BR />run ps -aux | grep syslog, make sure there IS no process running (don't trust the script), if there is manually kill it.<BR /><BR />Look at the file /var/run/syslogd.pid and see which process id it thinks syslogd is running under.<BR /><BR />If syslogd happened to be running, then kill it, move the messages file across to messages.bak and touch the messages file (giving it the same permissions/owner as the original messages file). Then try restarting syslogd.<BR /><BR />Good luck,<BR /><BR />Shane.<BR /><BR /> Wed, 10 Jul 2002 05:55:57 GMT https://community.hpe.com/t5/operating-system-linux/weird-problem-w-syslogd/m-p/2759438#M1895 Shane Hjorth 2002-07-10T05:55:57Z