supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Laurent Bercot <ska-supervision@skarnet.org>
Subject: Re: qpsmtpd-forkserver on Mac OS X
Date: Wed, 7 Jun 2006 11:20:29 +0200	[thread overview]
Message-ID: <20060607092029.GA31722@skarnet.org> (raw)
In-Reply-To: <75C12523-F011-4682-B172-728336E1B739@seespotcode.net>

> The server runs correctly when launched by the run script  
> (sudo ./run without the runit service running), but not when  
> controlled by runit. :/

 This is not the same.
 When you do "sudo ./run", the run script is executed with most of
your user environment (open fds, environment variables and whatnot),
modified in some way by the sudo configuration.
 When the run script is started by runit, it is run with a "boot"
environment: init spawns runsvdir, which spawns runsv, which spawns
your service.
 There's something in your service that works in a user environment
and doesn't in a boot environment. I don't know qpsmtpd at all, but
here are some random points:

 - Does your server work when stdin isn't a terminal? If not, why?
 - (depending on your boot configuration) Does your server work when
stdin is closed?
 - What do kernel limits look like in your boot environment? Are
there ulimit commands in log in scripts that make them less strict
in user environments?

 HTH,

-- 
 Laurent


  reply	other threads:[~2006-06-07  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05  8:58 Michael Glaesemann
2006-06-06 15:57 ` Gerrit Pape
2006-06-07  3:36   ` Michael Glaesemann
2006-06-07  9:20     ` Laurent Bercot [this message]
2006-06-07  9:54       ` Michael Glaesemann
2006-06-07 12:28         ` Charlie Brady
2006-06-07 13:40           ` Laurent Bercot
2006-10-12  6:56             ` Michael Glaesemann

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=20060607092029.GA31722@skarnet.org \
    --to=ska-supervision@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).