Difference between revisions of "Hall D account strategy"
From GlueXWiki
(→What probably will need) |
(→What we have NOW) |
||
Line 30: | Line 30: | ||
* Account called <b>halld</b> | * Account called <b>halld</b> | ||
:# Local account with a constant password | :# Local account with a constant password | ||
− | :# Owns files on <i>/group/halld-online</i> and <i>/group/halld/Online</i> | + | :# Owns files on <i>/group/halld-online</i> and <i>/group/halld/Online</i> , which computer center does not like. |
+ | |||
+ | * We can live with this until disk server and RAID didsks arrive, if computer center does not object. |
Latest revision as of 14:29, 16 January 2013
Hall D Online Account Strategy
What probably will need
- Account for Hall D software development : halldonline (or something)
- CUE account with changing password
- Only a few software developers know the password
- Used to build the online production software
- We could split the single development accounts into online subsystem accounts
- Probably not very useful
- Account for Hall D production running : halld (or something)
- Local account for production running
- All collaboration members will know the password.
- Does not have write permissions for files that are created in the production area by the development account(s)
- Will only own files on the Hall D fileserver and Hall D RAID disks. Ownership will need to change when the owned files are moved to other places.
What we have NOW
- Account called halldusers
- CUE account with moving password
- A few of us know the password pattern
- The name suggests that the account is there for "user"
- Account called halld
- Local account with a constant password
- Owns files on /group/halld-online and /group/halld/Online , which computer center does not like.
- We can live with this until disk server and RAID didsks arrive, if computer center does not object.