From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Fiona Klute via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v4 0/3] Refactor OpenSSH init.d script
Date: Tue, 9 Jul 2024 12:06:59 +0200 [thread overview]
Message-ID: <20240709120659.60e32214@windsurf> (raw)
In-Reply-To: <42d13dfb-0ac3-4939-b50b-a4187df30e89@gmx.de>
Hello Fiona,
On Tue, 9 Jul 2024 11:55:56 +0200
Fiona Klute <fiona.klute@gmx.de> wrote:
> The script is functional, but the use of long options was intentional
> for readability and I'd rather have it preserved. Having existing
> scripts in a hard-to-read style doesn't seem like a good reason not to
> be more explicit in new/updated ones [1]. That was the reason for the
> question (and patch) about which Busybox options I can rely on when
> writing init scripts.
>
> Regarding the added "-q", if a start (stop) command fails because an
> instance is already running (not running) with the current version you
> only get "Starting sshd: FAIL", while with my version you'd see the
> *reason* in start-stop-daemon output. That seems important to me. I only
> had "-q" in the reload function because the "stopping" output of
> start-stop-daemon (when it's actually just sending a SIGHUP) seemed like
> it might confuse someone.
I'm fine with both, but then I think the documentation and the
canonical example it refers to should be fixed first. This is how we
declare what is the "right" way of doing things. Otherwise, we'll keep
on using these as a reference for all future scripts, and we don't have
a reference point that tells us how things should be done when fixing
existing scripts or adding new ones.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-09 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 10:16 [Buildroot] [PATCH v4 0/3] Refactor OpenSSH init.d script Fiona Klute via buildroot
2024-07-04 10:16 ` [Buildroot] [PATCH v4 1/3] package/openssh: manage sshd using start-stop-daemon Fiona Klute via buildroot
2024-07-04 10:16 ` [Buildroot] [PATCH v4 2/3] package/openssh: fix init script indentation Fiona Klute via buildroot
2024-07-04 10:16 ` [Buildroot] [PATCH v4 3/3] package/openssh: implement "reload" using SIGHUP Fiona Klute via buildroot
2024-07-08 21:53 ` [Buildroot] [PATCH v4 0/3] Refactor OpenSSH init.d script Thomas Petazzoni via buildroot
2024-07-09 9:55 ` Fiona Klute via buildroot
2024-07-09 10:06 ` Thomas Petazzoni via buildroot [this message]
2024-07-09 11:31 ` Fiona Klute via buildroot
2024-07-09 11:44 ` yann.morin
2024-07-10 17:39 ` Fiona Klute via buildroot
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=20240709120659.60e32214@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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