From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] vzdump: remove usage examples involving 'notification-{target, policy}'
Date: Wed, 14 Feb 2024 10:07:38 +0100 [thread overview]
Message-ID: <20240214090738.57228-1-l.wagner@proxmox.com> (raw)
Also clarify in one example that using `--mailto` will bypass the
notification system (at least from the user's perspective).
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
vzdump.adoc | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/vzdump.adoc b/vzdump.adoc
index 24a3e80..b5bbac7 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -555,14 +555,12 @@ Use rsync and suspend/resume to create a snapshot (minimal downtime).
# vzdump 777 --mode suspend
Backup all guest systems and send notification mails to root and admin.
+Due to `mailto` being set and `notification-mode` being set to `auto` by
+default, the notification mails are sent via the system's `sendmail`
+command instead of the notification system.
# vzdump --all --mode suspend --mailto root --mailto admin
-Backup guest 777 and notify via the `notify-admins` notification target on
-failure.
-
- # vzdump 777 --notification-target notify-admins --notification-policy failure
-
Use snapshot mode (no downtime) and non-default dump directory.
# vzdump 777 --dumpdir /mnt/backup --mode snapshot
@@ -592,4 +590,3 @@ file system, using pipes
ifdef::manvolnum[]
include::pve-copyright.adoc[]
endif::manvolnum[]
-
--
2.39.2
next reply other threads:[~2024-02-14 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 9:07 Lukas Wagner [this message]
2024-02-20 15:15 ` [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=20240214090738.57228-1-l.wagner@proxmox.com \
--to=l.wagner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.