[chef] Re: About stopping the chef server instance (v0.7)

[dreamcat four < >]

$ pstree | less

To see the chain of process.

I guess chef now defaults to thin server. Previously mongrel.
(The thin server uses eventmachine to fork its processes.)

The lower number are often started before the higher number.
So maybe 8938 is the Process Group owner, and you might
kill that one. But its better to get from the PID file.

Depending the server, (thin, mongrel, unicorn), the pid file will
look a little bit different.

On Mon, Jan 18, 2010 at 3:19 AM, Dikang Gu 
<
 >
 wrote:
> Hi guys,
>
> When I run the "sudo chef-server -c2 -p 4002", I find that 4 processes are
> started:
>
> 
 :~$
>  sudo chef-server -c2 -p 4002
>  ~ In 8938
> 
 :~$
>  ps -e | grep ruby
>  3426 ?        00:00:07 ruby
>  4031 ?        00:02:57 ruby
>  4032 ?        00:00:00 ruby
>  4033 ?        00:00:00 ruby
>  8938 ?        00:00:00 ruby
>  8940 ?        00:00:00 ruby
>  8941 ?        00:00:00 ruby
>  8942 ?        00:00:00 ruby
>
> I know that the 8941 listens to the port 4002, and 8942 listens to 4003,
> but what are the 8938 and 8940 used for?
>
> If I'd like to stop this chef server instance, I have to stop the process
> 8940, right? why?
>
> Thanks
> Dikang
>
>