Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Salvatore Bonaccorso <carnil@debian.org>, NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org, Ben Hutchings <benh@debian.org>
Subject: Re: [PATCH nfs-utils] start-statd: Fix shellcheck warnings
Date: Mon, 17 Jul 2023 17:49:12 -0400	[thread overview]
Message-ID: <b2663a92-7947-d528-b852-fab3552ea867@redhat.com> (raw)
In-Reply-To: <20230709072028.829990-1-carnil@debian.org>



On 7/9/23 3:20 AM, Salvatore Bonaccorso wrote:
> From: Ben Hutchings <benh@debian.org>
> 
> shellcheck currently complains:
> 
> In utils/statd/start-statd line 14:
>         [ 1`cat /run/rpc.statd.pid` -gt 1 ] &&
>            ^----------------------^ SC2046 (warning): Quote this to prevent word splitting.
>            ^----------------------^ SC2006 (style): Use $(...) notation instead of legacy backticks `...`.
> 
> Did you mean:
>         [ 1$(cat /run/rpc.statd.pid) -gt 1 ] &&
> 
> In utils/statd/start-statd line 15:
>         kill -0 `cat /run/rpc.statd.pid` > /dev/null 2>&1
>                 ^----------------------^ SC2046 (warning): Quote this to prevent word splitting.
>                 ^----------------------^ SC2006 (style): Use $(...) notation instead of legacy backticks `...`.
> 
> Did you mean:
>         kill -0 $(cat /run/rpc.statd.pid) > /dev/null 2>&1
> 
> Use quotes and $() as recommended.
> 
> Signed-off-by: Ben Hutchings <benh@debian.org>
> Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
Committed (tag: nfs-utils-2-6-4-rc3)

steved.
> ---
>   utils/statd/start-statd | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/utils/statd/start-statd b/utils/statd/start-statd
> index 2baf73c385cf..b11a7d91a7f6 100755
> --- a/utils/statd/start-statd
> +++ b/utils/statd/start-statd
> @@ -11,8 +11,8 @@ exec 9> /run/rpc.statd.lock
>   flock -e 9
>   
>   if [ -s /run/rpc.statd.pid ] &&
> -       [ 1`cat /run/rpc.statd.pid` -gt 1 ] &&
> -       kill -0 `cat /run/rpc.statd.pid` > /dev/null 2>&1
> +       [ "1$(cat /run/rpc.statd.pid)" -gt 1 ] &&
> +       kill -0 "$(cat /run/rpc.statd.pid)" > /dev/null 2>&1
>   then
>       # statd already running - must have been slow to respond.
>       exit 0


      reply	other threads:[~2023-07-17 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09  7:20 [PATCH nfs-utils] start-statd: Fix shellcheck warnings Salvatore Bonaccorso
2023-07-17 21:49 ` Steve Dickson [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=b2663a92-7947-d528-b852-fab3552ea867@redhat.com \
    --to=steved@redhat.com \
    --cc=benh@debian.org \
    --cc=carnil@debian.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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