1846388 Members
3251 Online
110256 Solutions
New Discussion

Re: syslog daemon

 
Ravi_8
Honored Contributor

syslog daemon

Hi, all
does anybody knows how to stop and start the syslog daemon in HP.

thanx in advance
never give up
8 REPLIES 8
Marcin Wicinski
Trusted Contributor

Re: syslog daemon

Hi Ravi,

Restarting syslogd (should work):

# kill `cat /var/run/syslog.pid`
# /usr/sbin/syslogd -D


Later,
Marcin Wicinski
Alex Glennie
Honored Contributor

Re: syslog daemon

/sbin/init.d/syslogd [stop/start]
Andreas Voss
Honored Contributor

Re: syslog daemon

Hi,

this works also:

/sbin/init.d/syslogd stop # or start

Regards
Rainer von Bongartz
Honored Contributor

Re: syslog daemon

kill syslogd
kill `cat /var/run/syslog.pid`
restart syslogd
kill -HUP `cat /var/run/syslog.pid`

Regards
Rainer
He's a real UNIX Man, sitting in his UNIX LAN making all his UNIX plans for nobody ...
Shahul
Esteemed Contributor

Re: syslog daemon

Hi

This clearly mentioned in man page of syslogd. U can even see the different options of syslog daemon.

Best of luck

Shahul
Animesh Chakraborty
Honored Contributor

Re: syslog daemon

Hi Ravi,
Are these answeres not sufficient ?
or you want know something else ?
as you have not assigned 8-10 points to anyone !!


cheers
Animesh
Did you take a backup?
Ravi_8
Honored Contributor

Re: syslog daemon

Hi, Animesh
The answers what i got is not solving my problem. The problem is with our IBM product MQSeries.we stop the syslod deamon and start the MQSeries and syslog daemon at the same time. when we looked at MQ log file it will be empty. where as same situation in Solaris, Digital unix and AIX shows full details of MQ in its logfile. I am in touch with HP, let u know once this problem solved.

later..
never give up
Jordan Bean
Honored Contributor

Re: syslog daemon

Just a couple of questions:

To which facility is MQseries logging? Verify that /etc/syslog.conf has an appropriate entry.

Is MQseries using the syslog socket (udp 514) or the named pipe (/dev/log)? If syslogd is running with option -N, then it will not be listening to the socket. Also verify that /dev/log is at least chmod 622.