Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] squid: add sysv initscript
Date: Wed, 14 Jan 2015 20:51:51 +0100	[thread overview]
Message-ID: <20150114205151.18568a75@free-electrons.com> (raw)
In-Reply-To: <1421262884-5512-2-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Wed, 14 Jan 2015 16:14:44 -0300, Gustavo Zacarias wrote:

> diff --git a/package/squid/S97squid b/package/squid/S97squid
> new file mode 100755
> index 0000000..b30af5b
> --- /dev/null
> +++ b/package/squid/S97squid
> @@ -0,0 +1,40 @@
> +#!/bin/sh
> +
> +[ -x /usr/sbin/squid ] || exit 0
> +[ -f /etc/squid.conf ] || exit 0

I must say I'm not very happy with those "if something is missing,
let's bail out silently" tests. We're doing the same in other init
scripts (as we discussed on IRC), but I think we should probably
rethink that a bit, and at least display an error message.

Also, checking for /usr/sbin/squid sound a bit silly, since the init
script is installed by the squid package, which also has installed the
squid binary.

I've nonetheless applied. Follow-up patches welcome, maybe as part of a
more global overhaul of our init scripts.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-01-14 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 19:14 [Buildroot] [PATCH 1/2] squid: create a user/group Gustavo Zacarias
2015-01-14 19:14 ` [Buildroot] [PATCH 2/2] squid: add sysv initscript Gustavo Zacarias
2015-01-14 19:51   ` Thomas Petazzoni [this message]
2015-01-14 20:16     ` Gustavo Zacarias
2015-01-14 19:35 ` [Buildroot] [PATCH 1/2] squid: create a user/group 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=20150114205151.18568a75@free-electrons.com \
    --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