On Sun, Feb 28, 2010 at 08:58:55AM -0800, Vince Valenti wrote: > > > I'm actually no longer the maintainer of the port, but if you check > sockstat, you will notice the second process is the one that is actually > listening to the network, etc: > > # ps auxww|grep syslog > root 29196 0.0 0.0 > 5320 2172 ?? I 8:40AM 0:00.00 /usr/local/sbin/syslog-ng -p > /var/run/syslog.pid > root 29197 0.0 0.0 5320 2432 ?? Ss 8:40AM 0:00.04 > /usr/local/sbin/syslog-ng -p /var/run/syslog.pid > > # sockstat|grep > syslog > root syslog-ng 29197 3 dgram /var/run/log > root syslog-ng 29197 5 > stream /var/db/syslog-ng.ctl > root syslog-ng 29197 6 dgram > /var/run/logpriv > root syslog-ng 29197 7 udp4 *:514 *:* > > My guess is that > this is by design. In fact, I've checked syslog-ng on a Linux machine > (gasp) and it also runs two processes: > > root 30648 0.0 0.0 29428 868 ? S > 04:02 0:00 supervising syslog-ng > root 30649 0.0 0.0 35984 2404 ? Ss 04:02 > 0:06 /opt/syslog-ng/sbin/syslog-ng --no-caps
IIRC I've also seen that on Solaris.
pgpPO07AYYARD.pgp
Description: PGP signature
