From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 4/4] grub-btrfsd: Drop redundant used PIDFILE mechanism
Date: Thu, 28 Mar 2024 10:32:30 +0000 [thread overview]
Message-ID: <48254713-B470-481B-BA27-A8843C3BD508@ipfire.org> (raw)
In-Reply-To: <263de5edf5246d928423b7ca971f57c703de21d9.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
It is almost as if there is something good about having this review process :)
> On 27 Mar 2024, at 19:42, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> Am Mittwoch, dem 27.03.2024 um 10:15 +0000 schrieb Michael Tremer:
>>
>>
>>> On 27 Mar 2024, at 05:15, Stefan Schantl
>>> <stefan.schantl(a)ipfire.org> wrote:
>>>
>>> This case is already covered by the PID mechanism of the used
>>> functions
>>>
>>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>>> ---
>>> src/initscripts/system/grub-btrfsd | 5 ++---
>>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/src/initscripts/system/grub-btrfsd
>>> b/src/initscripts/system/grub-btrfsd
>>> index 26760f9be..5981c3a0a 100644
>>> --- a/src/initscripts/system/grub-btrfsd
>>> +++ b/src/initscripts/system/grub-btrfsd
>>> @@ -33,15 +33,14 @@ case "$1" in
>>> btrfs)
>>>
>>> boot_mesg "Starting GRUB/Btrfs Daemon..."
>>> - loadproc -b -p "$PIDFILE" /usr/bin/grub-btrfsd --syslog
>>> "$SNAPSHOTDIR"
>>> - echo "$!" > "$PIDFILE"
>>> + loadproc -b /usr/bin/grub-btrfsd --syslog "$SNAPSHOTDIR"
>>> ;;
>>> esac
>>> ;;
>>>
>>> stop)
>>> boot_mesg "Stopping grub-btrfsd..."
>>> - killproc -p "$PIDFILE" /usr/bin/grub-btrfsd
>>> + killproc -p /usr/bin/grub-btrfsd
>>> sleep 1;
>>
>> Why is there a sleep here?
> Good catch, that's a classical orphaned piece of code when removing
> some other stuff.
>
> I'll handle it in a v2 patchset.
>>
>>> ;;
>>>
>>> --
>>> 2.39.2
next prev parent reply other threads:[~2024-03-28 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 12:39 [PATCH 1/2] inotify-tools: New package Stefan Schantl
2024-03-24 12:39 ` [PATCH 2/2] grub-btrfs: " Stefan Schantl
2024-03-25 10:38 ` Michael Tremer
2024-03-27 5:15 ` [PATCH 1/4] initscripts: Add generic function to get the filesystem type of a volume Stefan Schantl
2024-03-27 5:15 ` [PATCH 2/4] grub-btrfsd: Use generic volume_fs_type function for FS detection Stefan Schantl
2024-03-27 5:15 ` [PATCH 3/4] grub-btrfsd: Adjust displayed starting message Stefan Schantl
2024-03-27 5:15 ` [PATCH 4/4] grub-btrfsd: Drop redundant used PIDFILE mechanism Stefan Schantl
2024-03-27 10:15 ` Michael Tremer
2024-03-27 19:42 ` Stefan Schantl
2024-03-28 10:32 ` Michael Tremer [this message]
2024-03-27 10:15 ` [PATCH 1/4] initscripts: Add generic function to get the filesystem type of a volume Michael Tremer
2024-03-27 19:43 ` Stefan Schantl
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=48254713-B470-481B-BA27-A8843C3BD508@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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