From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Multiple master processes
Date: Mon, 31 Jan 2011 18:08:15 +0000 [thread overview]
Message-ID: <20110131180815.GA17643@dcvr.yhbt.net> (raw)
In-Reply-To: <87ei7te76x.wl%tils@tils.net>
Tilmann Singer <tils@tils.net> wrote:
> Hi,
>
> I'm seeing the following output of ps after starting unicorn, which as
> I understand it means that there are multiple master processes
> running, each with its own pid. Is that normal behaviour or is there
> something wrong with my setup?
It's normal behavior for Linux 2.4.x + Ruby 1.9, don't worry about it.
> $ ps xf|grep 4002
> 8022 ? S 0:00 unicorn master -c config/unicorn.rb -E production -p 4002 -D
> 8024 ? S 0:00 \_ unicorn master -c config/unicorn.rb -E production -p 4002 -D
> 26743 ? S 0:00 | \_ unicorn master -c config/unicorn.rb -E production -p 4002 -D
> 26734 ? S 0:22 \_ unicorn worker[0] -c config/unicorn.rb -E production -p 4002 -D
> 26736 ? S 0:00 | \_ unicorn worker[0] -c config/unicorn.rb -E production -p 4002 -D
> 26739 ? S 0:00 | \_ unicorn worker[0] -c config/unicorn.rb -E production -p 4002 -D
> 26737 ? S 0:22 \_ unicorn worker[2] -c config/unicorn.rb -E production -p 4002 -D
> 26740 ? S 0:00 | \_ unicorn worker[2] -c config/unicorn.rb -E production -p 4002 -D
> 26741 ? S 0:00 | \_ unicorn worker[2] -c config/unicorn.rb -E production -p 4002 -D
> 26742 ? S 0:21 \_ unicorn worker[1] -c config/unicorn.rb -E production -p 4002 -D
> 26744 ? S 0:00 \_ unicorn worker[1] -c config/unicorn.rb -E production -p 4002 -D
> 26745 ? S 0:00 \_ unicorn worker[1] -c config/unicorn.rb -E production -p 4002 -D
> $ cat tmp/pids/unicorn.pid
> 8022
>
> This is on Linux 2.4.27, ruby 1.9.2
With LinuxThreads in 2.4, the native threads used by Ruby 1.9 each had a
unique PID and /proc entry whereas with NPTL in 2.6 hides the top-level
entries of tasks that weren't processes (still visible in
/proc/$pid/task/*)
"tasks" are just the in-kernel representation of either processes and
native threads in all Linux versions. They're created via the same
system call, clone(2), so pthread_create() and fork() are just wrappers
around clone() with different arguments. It's just 2.4 had fewer
options for clone() that made it weirder and less POSIX-conformant.
The pthreads(7) manpage has more details on the differences between NPTL
and LinuxThreads.
Wow, I didn't realize people ran the latest Rubies on 2.4.x!
--
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-01-31 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:47 Multiple master processes Tilmann Singer
2011-01-31 18:08 ` Eric Wong [this message]
2011-02-01 20:48 ` Tilmann Singer
2011-02-01 21:22 ` Eric Wong
2011-01-31 19:24 ` Jamie Wilkinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110131180815.GA17643@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).