All of lore.kernel.org
 help / color / mirror / Atom feed
From: rdkehn at yahoo.com <rdkehn@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 1/1] package/unscd: new package
Date: Wed, 23 Dec 2015 07:29:17 -0600	[thread overview]
Message-ID: <20151223132917.GA12918@dkarchlinux64.currentcomm.com> (raw)
In-Reply-To: <20151223141340.2add43fd@free-electrons.com>

Hi Thomas,

On Wed, Dec 23, 2015 at 02:13:40PM +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 23 Dec 2015 06:59:29 -0600, rdkehn at yahoo.com wrote:
> 
> > A PID file is created by unscd in /var/run/nscd/ when it is started.
> > The PID file is deleted when unscd is stopped; however, the
> > /var/run/nscd/ directory remains.
> > 
> > unscd can be started in debug mode (a.k.a foreground, -d option). In
> > doing so, PID file creation could be done in the init script as
> > requested. The problem I see here is that unscd logs to stderr when
> > started in debug mode.
> > 
> > Do you still prefer a patch for PID file creation in the init
> > script?
> 
> You can tell start-stop-daemon that the PID file is created by the
> daemon itself. Basically, pass just the -p <pid-file> option when
> starting and stopping the daemon. As long as you don't pass -m when
> starting the daemon, start-stop-daemon does not create the pid file.
> 
> See man start-stop-daemon(8) for all the details.
> 

Ah, you're not saying that you want stat-stop-daemon to create the
PID file. (It's early, coffee starting to kick in...)

Regards,
...doug

      reply	other threads:[~2015-12-23 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 14:56 [Buildroot] [PATCH v7 1/1] package/unscd: new package Doug Kehn
2015-12-02 21:54 ` Arnout Vandecappelle
2015-12-22 19:58 ` Thomas Petazzoni
2015-12-23 12:59   ` rdkehn at yahoo.com
2015-12-23 13:13     ` Thomas Petazzoni
2015-12-23 13:29       ` rdkehn at yahoo.com [this message]

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=20151223132917.GA12918@dkarchlinux64.currentcomm.com \
    --to=rdkehn@yahoo.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.