Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Tilman Keskinöz" <arved@arved.at>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Enable feature CONFIG_FEATURE_PIDFILE so that the syslog initscript actually works
Date: Thu, 28 Mar 2013 16:41:09 +0100	[thread overview]
Message-ID: <51546495.2070307@arved.at> (raw)
In-Reply-To: <5154614A.6030806@mind.be>

* Arnout Vandecappelle [Thu, 28 Mar 2013 16:27:06 +0100]:
>> If you don't want to enable this feature, another option would be to use
>> start-stop-daemon -p in the syslog init script.
> 
>  It is already using the -p option, no?

Sorry, i meant -m, e.g. let start-stop-daemon handle the pidfile creation.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130328/12366c96/attachment.asc>

  reply	other threads:[~2013-03-28 15:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 14:48 [Buildroot] [PATCH 1/4] Fix typo arved at arved.at
2013-03-25 14:48 ` [Buildroot] [PATCH 2/4] Support .dotfiles in / being copied to the TARGET arved at arved.at
2013-03-25 22:44   ` Peter Korsgaard
2013-03-25 14:48 ` [Buildroot] [PATCH 3/4] Fix path to pidfile arved at arved.at
2013-03-28  7:09   ` Arnout Vandecappelle
2013-03-31 18:59   ` Peter Korsgaard
2013-03-25 14:48 ` [Buildroot] [PATCH 4/4] Enable feature CONFIG_FEATURE_PIDFILE so that the syslog initscript actually works arved at arved.at
2013-03-28  7:12   ` Arnout Vandecappelle
2013-03-28 14:59     ` Tilman Keskinöz
2013-03-28 15:27       ` Arnout Vandecappelle
2013-03-28 15:41         ` Tilman Keskinöz [this message]
2013-03-25 16:52 ` [Buildroot] [PATCH 1/4] Fix typo Peter Korsgaard

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=51546495.2070307@arved.at \
    --to=arved@arved.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox