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 (VE7TFX/VE6BBM) <lyn...@orthanc.ca> wrote: > 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 depends on how you use them. The > main reason you might want to have different CPU server owners is > to control access to physical hardware. E.g. I have machines that > are used to control my radios via their serial and USB interfaces. > For those, I don't want the "general pupulation" to have access to > that hardware, so I run those servers under a userid that is distinct > from the "general purpose" CPU server owner. > > Oh, the Pi I use for bluetooth dev work has its own host owner, > for similar reasons. > > I'm sure there are other cases, but that's the only one where I've > personally had a need for multiple host owners. > > --lyndon > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T690e4304847a34e4-M17036caa82debd1aa65af977 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
