From: Marco Feichtinger <marco@germteig.com>
To: 9fans <9fans@9fans.net>
Subject: [9fans] different users for different system roles
Date: Fri, 10 Feb 2023 09:15:23 +0100 [thread overview]
Message-ID: <DD45CA5A-4167-4892-A296-6314F049E85C@germteig.com> (raw)
If you have a grid with multiple machines, each with a dedicated system role,
should each system role get his own user?
Like one user for file servers, one for auth, one for venti, and one for cpu servers.
Is there any point in doing that or is it better to only use one user (bootes)
on all these machines?
-marco
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T690e4304847a34e4-Mf8fd9ae58f133ff67ff1ae42
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2023-02-10 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 8:15 Marco Feichtinger [this message]
2023-02-10 9:30 ` Frank D. Engel, Jr.
2023-02-10 11:19 ` hiro
2023-02-14 0:45 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2023-02-14 10:54 ` hiro
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=DD45CA5A-4167-4892-A296-6314F049E85C@germteig.com \
--to=marco@germteig.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).