agreed. compartmentalization might be used to have less
users/passwords than servers. if two cpu servers are used
interchangably for the same usecase by the same end-users, why not
give them the same credentials.
next time please try to quote correctly, lyndon.
On 2/14/23, Lyndon Nerenberg (VE7TF
hiro writes:
> > 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.
My was has always been to have a file system user and an auth server
user that are used ONLY for those roles.
As for CPU servers, it really
> 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
Yes, if you share one authserver, then you'd have to use different
users in order to be allowed to use different passwords. If yo
I'm not sure what the prevailing wisdom on this is at this time, but for
whatever it may be worth[less], my own small cluster I have set up with
a separate host owner per system role (one for the file server, one for
the auth server, and one used by both of my CPU servers). I'm not
currently u
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 thes
