From: Dylan Whyte <d.whyte@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH docs 6/7] Remove reference to backup@pam & old console msg
Date: Fri, 6 Nov 2020 15:46:29 +0100 [thread overview]
Message-ID: <20201106144630.21538-7-d.whyte@proxmox.com> (raw)
In-Reply-To: <20201106144630.21538-1-d.whyte@proxmox.com>
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
docs/backup-client.rst | 7 +------
docs/managing-remotes.rst | 2 +-
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/docs/backup-client.rst b/docs/backup-client.rst
index a23535fa..0e6b1b70 100644
--- a/docs/backup-client.rst
+++ b/docs/backup-client.rst
@@ -106,10 +106,6 @@ In the following examples we use ``backup-server:store1``.
# proxmox-backup-client backup root.pxar:/ --repository backup-server:store1
Starting backup: host/elsa/2019-12-03T09:35:01Z
Client name: elsa
- skip mount point: "/boot/efi"
- skip mount point: "/dev"
- skip mount point: "/run"
- skip mount point: "/sys"
Uploaded 12129 chunks in 87 seconds (564 MB/s).
End Time: 2019-12-03T10:36:29+01:00
@@ -117,8 +113,7 @@ This will prompt you for a password and then uploads a file archive named
``root.pxar`` containing all the files in the ``/`` directory.
.. Caution:: Please note that the proxmox-backup-client does not
- automatically include mount points. Instead, you will see a short
- ``skip mount point`` notice for each of them. The idea is to
+ automatically include mount points. The idea is to
create a separate file archive for each mounted disk. You can
explicitly include them using the ``--include-dev`` option
(i.e. ``--include-dev /boot/efi``). You can use this option
diff --git a/docs/managing-remotes.rst b/docs/managing-remotes.rst
index 1b32d40b..e29ae37f 100644
--- a/docs/managing-remotes.rst
+++ b/docs/managing-remotes.rst
@@ -86,7 +86,7 @@ For setting up sync jobs, the configuring user needs the following permissions:
If the ``remove-vanished`` option is set, ``Datastore.Prune`` is required on
the local datastore as well. If the ``owner`` option is not set (defaulting to
-``backup@pam``) or set to something other than the configuring user,
+``root@pam``) or set to something other than the configuring user,
``Datastore.Modify`` is required as well.
.. note:: A sync job can only sync backup groups that the configured remote's
--
2.20.1
next prev parent reply other threads:[~2020-11-06 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:46 [pbs-devel] [PATCH docs 0/7] Update for new content and sections Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 1/7] installation & gui: Formatting fixup Dylan Whyte
2020-11-06 15:51 ` Dietmar Maurer
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 2/7] backup-client: add section on change-owner command Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 3/7] datastore: description of new datastore view Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 4/7] Update where to find certain items since GUI update Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 5/7] maintenance: add verification and prune to section Dylan Whyte
2020-11-06 14:46 ` Dylan Whyte [this message]
2020-11-06 15:34 ` [pbs-devel] [PATCH docs 6/7] Remove reference to backup@pam & old console msg Dietmar Maurer
2020-11-09 7:38 ` Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 7/7] Add screenshots Dylan Whyte
2020-11-06 15:33 ` [pbs-devel] applied: [PATCH docs 0/7] Update for new content and sections Dietmar Maurer
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=20201106144630.21538-7-d.whyte@proxmox.com \
--to=d.whyte@proxmox.com \
--cc=pbs-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.