From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Dominic Jäger" <d.jaeger@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm
Date: Wed, 22 Jul 2020 12:31:53 +0200 [thread overview]
Message-ID: <94ed3288-870c-af50-f4a6-c0b03b1b30e8@proxmox.com> (raw)
In-Reply-To: <20200722102052.25546-1-d.jaeger@proxmox.com>
On 22.07.20 12:20, Dominic Jäger wrote:
> /etc/corosync/* includes the directory uidgid.d.
> Consequentlly, a correct rm call requires -r.
Does leaving this directory left-over causes any issues?
IIRC, I omit the "-r" explicitly as there can be also a directory from
a qdevice or other ones, which we do not want to remove - to level
corosync/* files where all desired to be removed, thus this rm varian.
But, maybe we should rather change it to:
# rm -f /etc/corosync/corosync.conf /etc/corosync/authkey
to make that more explicit
>
> Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com>
> ---
> pvecm.adoc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/pvecm.adoc b/pvecm.adoc
> index 4bf2f59..9207571 100644
> --- a/pvecm.adoc
> +++ b/pvecm.adoc
> @@ -414,7 +414,7 @@ Delete the corosync configuration files:
> [source,bash]
> ----
> rm /etc/pve/corosync.conf
> -rm /etc/corosync/*
> +rm -r /etc/corosync/*
> ----
>
> You can now start the filesystem again as normal service:
>
next prev parent reply other threads:[~2020-07-22 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:20 Dominic Jäger
2020-07-22 10:20 ` [pve-devel] [PATCH docs 2/2] pvecm: Add output for delnode Dominic Jäger
2020-08-20 13:31 ` [pve-devel] applied: " Thomas Lamprecht
2020-07-22 10:31 ` Thomas Lamprecht [this message]
2020-07-23 7:17 ` [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm Dominic Jäger
2020-08-20 13:31 ` [pve-devel] applied: " Thomas Lamprecht
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=94ed3288-870c-af50-f4a6-c0b03b1b30e8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.jaeger@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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