Hall D account strategy

Hall D Online Account Strategy

What probably will need

• Account for Hall D software development : halldonline (or something)

1. CUE account with changing password
2. Only a few software developers know the password
3. Used to build the online production software

• We could split the single development accounts into online subsystem accounts

1. Probably not very useful

• Account for Hall D production running : halld (or something)

1. Local account for production running
2. All collaboration members will know the password.
3. Does not have write permissions for files that are created in the production area by the development account(s)
4. 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

1. CUE account with moving password
2. A few of us know the password pattern
3. The name suggests that the account is there for "user"

• Account called halld

1. Local account with a constant password
2. 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.