Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/transmission: fix sysv init script (name vs. exec)
Date: Sun, 21 Mar 2021 16:19:52 +0100	[thread overview]
Message-ID: <20210321161952.447ed460@gmx.net> (raw)
In-Reply-To: <87sg4qu7ef.fsf@dell.be.48ers.dk>

Hello Peter,

On Fri, 19 Mar 2021 23:04:56 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
>
>  > - fix sysv init script in case package start-stop-daemon is
>  >   enabled
>
>  > Fixes:
>
>  >   - https://bugs.busybox.net/show_bug.cgi?id=13576
>
>  >   $ /etc/init.d/S92transmission stop
>  >   Stopping bittorrent client transmission-daemon...
>  >   start-stop-daemon: warning: this system is not able to track process names
>  >   longer than 15 characters, please use --exec instead of --name.
>
>  > Reported-by: ingineru_de_sistem at yahoo.com
>  > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>  > ---
>  > Changes v1 -> v2:
>  >   - add reported-by and reference to bug entry
>
> Committed to 2020.02.x, 2020.11.x and 2021.02.x, thanks.
>
> grepping the source tree, it looks like we have a similar issue in
> rng-tools:
>
> git grep 'start-stop-daemon.*-K.*-n'
> package/rng-tools/S21rngd:      if start-stop-daemon -K -q -s KILL -p "${PID_FILE}" -n "${NAME}"; then

Did not catch it because I grep'ed only for the long version...

>
> Care to send a fix for that as well?
>

Rngd is not affected as the NAME ('rngd') is below the 15 characters limit...,
should I change to exec anyway?

Regards,
Peter

      reply	other threads:[~2021-03-21 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 22:41 [Buildroot] [PATCH v2] package/transmission: fix sysv init script (name vs. exec) Peter Seiderer
2021-03-11 21:55 ` Yann E. MORIN
2021-03-19 22:04 ` Peter Korsgaard
2021-03-21 15:19   ` Peter Seiderer [this message]

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=20210321161952.447ed460@gmx.net \
    --to=ps.report@gmx.net \
    --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