This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Donna, >Date: Thu, 13 Oct 2005 15:37:30 -0600 >From: "Kliche, Donna V." <address@hidden> >Organization: South Dakota School of Mines and Technology >To: "Steve Emmerson" <address@hidden> >Subject: RE: hupsyslog(1) using killall(1) under SUSE (was: LDM-6.4.1 >instalation) The above message contained the following: > ldm@squall:~> ls -l /etc/*syslog* > total 16 > -rw-r--r-- 1 root root 4748 2005-07-05 09:37 syslog-ng.conf > -rw-r--r-- 1 root root 4510 2005-03-19 13:23 syslog-ng.conf.in The above are the current and previous syslog-ng(8) configuration-files. > ldm@squall:~> ls -l /var/run/*syslog* > -rw------- 1 root root 5 2005-10-12 09:13 /var/run/syslog-ng.pid Great! The above file should contain the PID of the syslog-ng process. What's the output of the command cat /var/run/syslog-ng.pid > ldm@squall:~> ps -ef|grep syslog > root 3692 1 0 Oct12 ? 00:00:00 /sbin/syslog-ng > ldm 18141 7439 0 15:37 pts/3 00:00:00 grep syslog > ldm@squall:~>=20 Regards, Steve Emmerson