From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Lorenz Stechauner <l.stechauner@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/1] pveum: add warning for disabling or deleting users
Date: Mon, 21 Jun 2021 09:53:40 +0200 [thread overview]
Message-ID: <27ec91a6-ff4b-dad5-b6c5-9f0602df9fb1@proxmox.com> (raw)
In-Reply-To: <20210520135342.58549-3-l.stechauner@proxmox.com>
On 20.05.21 15:53, Lorenz Stechauner wrote:
> see #3101
>
> Signed-off-by: Lorenz Stechauner <l.stechauner@proxmox.com>
> ---
> pveum.adoc | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/pveum.adoc b/pveum.adoc
> index 7120db7..0bece8a 100644
> --- a/pveum.adoc
> +++ b/pveum.adoc
> @@ -56,6 +56,11 @@ Each user entry in this file contains the following information:
> * Whether this user is enabled or disabled
> * Optional two-factor authentication keys
>
> +CAUTION: After disabling or deleting a user, this user will not be able to
> +log in to new sessions or start new tasks. But all tasks which already have
> +been started by this user (e.g. terminal sessions) will **not** be
See the internal style guide regarding some style rules we want to enforce for
new additions (and slowly change over existing ones), here the section regarding
e.g./i.e.:
https://intranet.proxmox.com/index.php/Technical_Writing_Style_Guide#e.g..2Fi.e.
But the whole thing is not that long, so I'd really recommend giving it a full
read.
> +terminated automatically.
> +
>
> System administrator
> ~~~~~~~~~~~~~~~~~~~~
>
prev parent reply other threads:[~2021-06-21 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 13:53 [pve-devel] [PATCH-SERIES manager/docs] " Lorenz Stechauner
2021-05-20 13:53 ` [pve-devel] [PATCH manager 1/1] ui: dc/UserEdit: add warning for disabling users Lorenz Stechauner
2021-05-20 13:53 ` [pve-devel] [PATCH docs 1/1] pveum: add warning for disabling or deleting users Lorenz Stechauner
2021-06-21 7:53 ` Thomas Lamprecht [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=27ec91a6-ff4b-dad5-b6c5-9f0602df9fb1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.stechauner@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