This commit is contained in:
felixfontein
2026-03-12 09:22:03 +00:00
parent 92dc99c05f
commit 361214c344
12 changed files with 23 additions and 12 deletions

View File

@@ -267,6 +267,7 @@ see <a class="reference internal" href="#ansible-collections-community-crypto-op
</div></td>
<td><div class="ansible-option-cell"><p>Name of the group that should own the filesystem object, as would be fed to <code class="docutils literal notranslate"><span class="pre">chown</span></code>.</p>
<p>When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership.</p>
<p>Specifying a numeric group name (for example, “1000”) will be assumed to be a group ID (GID) and not a group name. To prevent confusion, avoid using purely numeric group names.</p>
</div></td>
</tr>
<tr class="row-even"><td><div class="ansible-option-cell">
@@ -288,7 +289,7 @@ see <a class="reference internal" href="#ansible-collections-community-crypto-op
</div></td>
<td><div class="ansible-option-cell"><p>Name of the user that should own the filesystem object, as would be fed to <code class="docutils literal notranslate"><span class="pre">chown</span></code>.</p>
<p>When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership.</p>
<p>Specifying a numeric username will be assumed to be a user ID and not a username. Avoid numeric usernames to avoid this confusion.</p>
<p>Specifying a numeric username (for example, “1000”) will be assumed to be a user ID (UID) and not a username. To prevent confusion, avoid using purely numeric usernames.</p>
</div></td>
</tr>
<tr class="row-even"><td><div class="ansible-option-cell">