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 v2] package/transmission: fix sysv init script (name vs. exec)
Date: Thu, 11 Mar 2021 22:55:19 +0100	[thread overview]
Message-ID: <20210311215519.GZ2737665@scaer> (raw)
In-Reply-To: <20210310224155.8138-1-ps.report@gmx.net>

Peter, All,

On 2021-03-10 23:41 +0100, Peter Seiderer spake thusly:
> - 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>

Applied to master, after rewordign the commit log to also include the
referecnes to upstream changes. Thanks.

Regards,
Yann E. MORIN.

> ---
> Changes v1 -> v2:
>   - add reported-by and reference to bug entry
> ---
>  package/transmission/S92transmission | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/transmission/S92transmission b/package/transmission/S92transmission
> index 29d7cd5863..85ff40ec16 100644
> --- a/package/transmission/S92transmission
> +++ b/package/transmission/S92transmission
> @@ -93,7 +93,7 @@ stop()
>          #   1 if daemon was already stopped
>          #   2 if daemon could not be stopped
>          #   other if a failure occurred
> -        start-stop-daemon --stop --quiet --retry=TERM/10/KILL/5 --pidfile $PIDFILE --name $NAME
> +        start-stop-daemon --stop --quiet --retry=TERM/10/KILL/5 --pidfile $PIDFILE --exec $DAEMON
>          RETVAL="$?"
>          [ "$RETVAL" = 2 ] && return 2
>  
> -- 
> 2.30.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2021-03-11 21:55 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 [this message]
2021-03-19 22:04 ` Peter Korsgaard
2021-03-21 15:19   ` Peter Seiderer

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=20210311215519.GZ2737665@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