Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Feb 2010 10:38:00 -0500
From:      Sean McAfee <smcafee@collaborativefusion.com>
To:        Marin Atanasov <dnaeon@gmail.com>
Cc:        Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de>, freebsd-ports@freebsd.org
Subject:   Re: sysutils/syslog-ng3 processes
Message-ID:  <4B87EAD8.3040105@collaborativefusion.com>
In-Reply-To: <717f7a3e1002260728h79fe50f3i576a2627ee19ce58@mail.gmail.com>
References:  <717f7a3e1002260651k1ce06986u4332c637b94d07ce@mail.gmail.com>	<20100226151612.GC93856@wep4035.physik.uni-wuerzburg.de> <717f7a3e1002260728h79fe50f3i576a2627ee19ce58@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Marin Atanasov wrote:
> On Fri, Feb 26, 2010 at 5:16 PM, Alexey Shuvaev <
> shuvaev@physik.uni-wuerzburg.de> wrote:
> 
>> On Fri, Feb 26, 2010 at 04:51:25PM +0200, Marin Atanasov wrote:
>>> Hello,
>>>
>>> I've noticed that when I start syslog-ng3 daemon it starts two processes.
>> I
>>> haven't seen this when running syslog-ng.
>>>
>>> Here are the processes:
>>>
>>> root     554  0.0  0.1  5320  2092  ??  I     4:46PM   0:00.00
>>> /usr/local/sbin/syslog-ng -p /var/run/syslog.pid
>>> root     555  0.0  0.1  5320  2456  ??  Ss    4:46PM   0:00.02
>>> /usr/local/sbin/syslog-ng -p /var/run/syslog.pid
>>>
>>> I was wondering why it actually start two (identical?) processes? Anyone
>> has
>>> an idea? Is this normal?
>>>
>> I think this would happen if you have two different scripts in
>> /usr/local/etr/rc.d that launch the same daemon. I think the names
>> of the scripts do not matter here. Do you have any stale rc.d scripts
>> in /usr/local/etr/rc.d?
>>
>> HTH,
>> Alexey.
>>
> 
> 
> Hi,
> 
> The system is a fresh 8.0 install. I've only syslog-ng rc.d script in
> /usr/local/etc/rc.d.
> 
> Didn't find anything reported about this. Could it be a port bug or
> something?
> 
> Regards,
> 

I can confirm this behavior on multiple clean 8.0 + syslog3 installs.

I really didn't do any investigation and just chalked it up to a change 
in behavior in syslog 3.x.

-- 
Sean McAfee
Senior Systems Engineer




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B87EAD8.3040105>