Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] modem-manager: fix test of unset variable in init script
Date: Sun, 15 Apr 2018 20:58:28 +0200	[thread overview]
Message-ID: <20180415185828.GD21958@scaer> (raw)
In-Reply-To: <20180415201808.013e84f3@windsurf.numericable.fr>

Thomas, All,

On 2018-04-15 20:18 +0200, Thomas Petazzoni spake thusly:
> On Sun, 15 Apr 2018 12:31:49 -0300 (BRT), Carlos Santos wrote:
> > >> +MODEMMANAGER_BIN=/usr/sbin/ModemManager
> > >>  PIDFILE=/var/run/ModemManager.pid
> > >>  
> > >>  [ -x $MODEMMANAGER_BIN ] || exit 0  
> > > 
> > > In fact, I think this test doesn't make sense. It just exits without
> > > any error if the binary doesn't exists, which is silly.
> > > 
> > > I'm advocating for removing such tests altogether, which would make the
> > > MODEMMANAGER_BIN variable unnecessary.  
> > 
> > I think the original purpose of these test was allowing the user to
> > disable the service by chmod'ing -x the executable file. We discussed
> > a similar situation in
> > 
> >    https://patchwork.ozlabs.org/patch/818897/
> > 
> > [which by the way is still in my endless to-do list]
> 
> Well, if you look at my feedback on this patch, I was already saying
> that the test to check whether radvd was executable or not was not
> useful.
> 
> I don't think making a binary program non-executable as a way of
> disabling its startup at boot time is very common. Probably a
> ENABLED=true/false variable in /etc/default/<service> is more common.
> 
> So, I think we should remove all those [ -x /usr/sbin/<foo> ] checks in
> our init scripts.
> 
> Cc'ing Peter, Arnout and Yann to gather additional opinions on this.

I agree with Thomas.

This is a position we already stated quite a few times in the past.

If one does not want the daemon, then just remove it and the init script
from a post-build script. If it is about debugging, just remove the
startup script on the target, or just 'exit 0' at the top of it.

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-04-15 18:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13 16:25 [Buildroot] [PATCH 0/2] Fix/improve modem-manager init script Carlos Santos
2018-04-13 16:25 ` [Buildroot] [PATCH 1/2] modem-manager: fix test of unset variable in " Carlos Santos
2018-04-14 16:07   ` Thomas Petazzoni
2018-04-15 15:31     ` Carlos Santos
2018-04-15 18:18       ` Thomas Petazzoni
2018-04-15 18:58         ` Yann E. MORIN [this message]
2018-04-15 20:22           ` Carlos Santos
2018-04-16 15:53             ` Arnout Vandecappelle
2018-05-14  6:57               ` Thomas Petazzoni
2018-05-14 11:21                 ` Carlos Santos
2018-04-13 16:25 ` [Buildroot] [PATCH 2/2] modem-manager: support a defaults file in the " Carlos Santos

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=20180415185828.GD21958@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