From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] dhcpcd: add SysV start-up script
Date: Sat, 4 Nov 2017 23:03:31 +0100 [thread overview]
Message-ID: <20171104230331.7ee309cb@windsurf> (raw)
In-Reply-To: <3f7fff7b-be5a-42ff-985f-0e860c98acb3@mind.be>
Hello,
On Sat, 4 Nov 2017 20:56:55 +0100, Arnout Vandecappelle wrote:
> I vaguely remember a recently added package where the daemon would silently
> fail to start if the config file is missing, and which doesn't even have a
> default config file. So I think checking for existence of the config file in the
> init script (if the config file is mandatory) makes sense.
So I suppose your suggestion is that the init script should abort with
a failure if the configuration file doesn't exist. Correct?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-04 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 22:36 [Buildroot] [PATCH 0/2] dhcpcd: start-up scripts Markus Mayer
2017-10-31 22:36 ` [Buildroot] [PATCH 1/2] dhcpcd: add SysV start-up script Markus Mayer
2017-11-02 22:06 ` Thomas Petazzoni
2017-11-02 22:18 ` Yann E. MORIN
2017-11-02 22:23 ` Thomas Petazzoni
2017-11-03 16:10 ` Yann E. MORIN
2017-11-03 16:17 ` Thomas Petazzoni
2017-11-03 16:31 ` Yann E. MORIN
2017-11-04 19:56 ` Arnout Vandecappelle
2017-11-04 22:03 ` Thomas Petazzoni [this message]
2017-11-04 22:07 ` Arnout Vandecappelle
2017-11-04 22:22 ` Thomas Petazzoni
2017-11-05 8:16 ` Yann E. MORIN
2017-11-05 8:10 ` Yann E. MORIN
2017-11-05 12:18 ` Arnout Vandecappelle
2017-11-05 13:24 ` Thomas Petazzoni
2017-11-05 13:28 ` Yann E. MORIN
2017-11-03 15:59 ` Peter Korsgaard
2017-10-31 22:36 ` [Buildroot] [PATCH 2/2] dhcpcd: add systemd start-up service Markus Mayer
2017-11-02 22:06 ` Thomas Petazzoni
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=20171104230331.7ee309cb@windsurf \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox