supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Mike Buland <xagafinelle@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: What is the process group hack
Date: Thu, 26 Apr 2012 09:52:12 -0600	[thread overview]
Message-ID: <CAK2oqqLyOvxi-hbUeOC_bjSt5qACB2iE=OS7VzOJueJSeJrHDg@mail.gmail.com> (raw)
In-Reply-To: <CAFUoqbfjBoBAu3h-+CvD9CXvV3YEEbPgzSyL1qHKreitLi870A@mail.gmail.com>

Hello,

At least one good example is getty processes.  There are a number of
systems (including newer linux kernels, but this may be optional) that
will not allow a process that is not the parent of it's own process
group to take an unclaimed terminal device as it's controlling
terminal.  getty programs don't generally make their own process
groups, and neither does runit for it's services, so the program group
hack is necessary to run a getty program on many systems.

Although I believe that you're right, it was intended in daemontools
as a way to try to supervise a process that wanted to daemonize, I've
never had experience using it in that capacity myself.

--Mike Buland

On Thu, Apr 26, 2012 at 9:15 AM, harish badrinath
<harishbadrinath@gmail.com> wrote:
> Hello,
>
> I Could not figure out what "process group hack" is supposed to be
> utilized for ??
> Is it used to supervise daemons that stubbornly fork into the background.
> Could anyone please explain with an example, i would be really helpful.
> I have to the best of my abilities RTFM'ed and searched the internet.
>
> Thank you,
> Harish


  reply	other threads:[~2012-04-26 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:15 harish badrinath
2012-04-26 15:52 ` Mike Buland [this message]
2012-04-26 18:27 ` Wayne Marshall
2012-04-26 19:02   ` Charlie Brady
2012-04-27  1:20   ` Laurent Bercot

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK2oqqLyOvxi-hbUeOC_bjSt5qACB2iE=OS7VzOJueJSeJrHDg@mail.gmail.com' \
    --to=xagafinelle@gmail.com \
    --cc=supervision@list.skarnet.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.
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 NNTP newsgroup(s).