From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] dhcpcd: add SysV start-up script
Date: Fri, 3 Nov 2017 17:31:34 +0100 [thread overview]
Message-ID: <20171103163134.GC3387@scaer> (raw)
In-Reply-To: <20171103171748.0111e6b0@windsurf>
Thomas, All,
On 2017-11-03 17:17 +0100, Thomas Petazzoni spake thusly:
> On Fri, 3 Nov 2017 17:10:57 +0100, Yann E. MORIN wrote:
>
> > > So you want explicitly handling for the "missing configuration file"
> > > situation in the init script?
> > >
> > > I wanted to avoid explicit handling, and just let the daemon whine (or
> > > not) if its config file is missing.
> >
> > The idea is that the script contains sensible defaults, but scans an
> > optional file (e.g. /etc/default.d/my-daemon.conf) that a user can
> > provide to override the defaults.
> >
> > IIRC, that's what was discussed and concluded a while ago (2 years?).
> >
> > I would like that users can change the behaviour of a service without
> > having to sed/replace the init script.
>
> I think we're not talking about the same thing. I'm not talking
> about /etc/default/foobar containing additional shell variables to
> tweak the init script behavior.
>
> I'm talking about the configuration file read by the daemon itself
> (/etc/lighttpd/lighttpd.conf for example).
Ah, I see, yes. In that case, the .mk should have installed a default
one, so we should not check.
So yes, the rule is that whatever should be installed by the .mk should
not be checked for by the initscript.
/me hands a lighted match to Thomas...
Kill it with fire!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-11-03 16:31 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 [this message]
2017-11-04 19:56 ` Arnout Vandecappelle
2017-11-04 22:03 ` Thomas Petazzoni
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=20171103163134.GC3387@scaer \
--to=yann.morin.1998@free.fr \
--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