From: Arnout Vandecappelle <arnout@mind.be>
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:27:06 +0100 [thread overview]
Message-ID: <5154614A.6030806@mind.be> (raw)
In-Reply-To: <51545AD6.5050307@arved.at>
On 28/03/13 15:59, Tilman Keskin?z wrote:
> Hi Arnout,
>
> * Arnout Vandecappelle [Thu, 28 Mar 2013 08:12:38 +0100]:
>>> -# CONFIG_FEATURE_PIDFILE is not set
>>> +CONFIG_FEATURE_PIDFILE=y
>>
>> Since we care very much about the size of busybox, could you evaluate
>> what the size difference is before and after this change? One smallish
>> architecture (e.g. ARM) is enough.
>>
>> Could you also make this change to the other busybox versions as well?
>> The different busybox configs should only differ because of features
>> added/removed in that particular version.
>
> On ARM the difference is 64 Bytes. (gcc 4.6.x)
Great, then it is a good idea to enable it by default. Can you do it
for all busybox versions?
Question to the list: do we really need to keep several busybox
versions? For U-Boot or kernel it may make some kind of sense, because
you have custom patches on top of a specific version. But for busybox?
> 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?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-03-28 15:27 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 [this message]
2013-03-28 15:41 ` Tilman Keskinöz
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=5154614A.6030806@mind.be \
--to=arnout@mind.be \
--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