From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] modem-manager: support a defaults file in the init script
Date: Sat, 21 Apr 2018 15:19:40 +0200 [thread overview]
Message-ID: <20180421131939.GA13287@x230> (raw)
In-Reply-To: <20180421130010.7702-1-casantos@datacom.ind.br>
Hi Carlos,
> Sometimes it is useful to pass some parameters to ModemManager when it
> starts (e.g. --log-level). Allow the user add a file with such flags in
> a MODEMMANAGER_ARGS variable. This is simpler than overriding the whole
> startup script (e.g. by means of a rootfs overlay).
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> Changes v1->v2
> - Rebase after commit ef0b7e7521 (modem-manager: don't test if the
> binary exists in the init script).
> ---
> package/modem-manager/S44modem-manager | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
> diff --git a/package/modem-manager/S44modem-manager b/package/modem-manager/S44modem-manager
> index a3f5003aa1..416c1e2ee6 100755
> --- a/package/modem-manager/S44modem-manager
> +++ b/package/modem-manager/S44modem-manager
> @@ -3,13 +3,16 @@
> # Starts ModemManager
> +# Allow a few customizations from a config file
> +test -r /etc/default/ModemManager && . /etc/default/ModemManager
> +
Out of curiosity, what is supposed to be in /etc/default/ModemManager ?
> PIDFILE=/var/run/ModemManager.pid
> start() {
> printf "Starting ModemManager: "
> umask 077
> start-stop-daemon -S -q -b -m -p $PIDFILE \
> - --exec /usr/sbin/ModemManager
> + --exec /usr/sbin/ModemManager -- $MODEMMANAGER_ARGS
LGTM.
> [ $? = 0 ] && echo "OK" || echo "FAIL"
> }
> stop() {
Kind regards,
Petr
next prev parent reply other threads:[~2018-04-21 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 13:00 [Buildroot] [PATCH v2] modem-manager: support a defaults file in the init script Carlos Santos
2018-04-21 13:19 ` Petr Vorel [this message]
2018-04-21 22:48 ` Carlos Santos
2018-04-22 19:37 ` Petr Vorel
2018-04-22 21:38 ` 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=20180421131939.GA13287@x230 \
--to=petr.vorel@gmail.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