supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jussi Ramo <jussi.ramo@ericsson.com>
Cc: supervision@list.skarnet.org
Subject: Re: duplicate processes
Date: Wed, 28 Sep 2005 11:25:20 +0300	[thread overview]
Message-ID: <433A5370.9070903@ericsson.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0509270956510.18597@e-smith.charlieb.ott.istop.com>

Thanks Charlie!

Charlie Brady wrote:
> 
> No, I didn't mean to suggest that runsv dies. I expect that ndb_mgmd has 
> forked, and the parent died. Perhaps it was designed to do that, to 
> "daemonise" the child. You will have to find some way to prevent that 
> from happening.
> 

That was it!! There is an option --nodeamon, and when using that 
everything works fine. (same goes for snmpdm -d)

 >mysql is known to be badly designed wrt co-operating with runit/daemontools.

Is it just because of this daemonizing issue, or is there other reasons 
not to use runit with mysql? If not, I could send those runs scripts to 
run script collection page when they are mature. I am using SUSE 9.1 and SLES.

Regards,
Jussi





  reply	other threads:[~2005-09-28  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27  8:36 Jussi Ramo
2005-09-27 18:25 ` Charlie Brady
2005-09-28  8:25   ` Jussi Ramo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-17  4:46 new "sv status" flags and exit-tracking patch, and misc Charles Duffy
2005-09-19  8:31 ` Gerrit Pape
2005-09-19 16:04   ` Charles Duffy
2005-09-19 19:13     ` Charles Duffy
2005-09-26 10:12       ` Gerrit Pape
2005-09-26 15:31         ` duplicate processes Jussi Ramo
2005-09-26 15:42           ` Charlie Brady

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=433A5370.9070903@ericsson.com \
    --to=jussi.ramo@ericsson.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).