Difference between revisions of "GlueX-related shared accounts on the JLab CUE"
(consolidate the two pages) |
(→How to log into the account) |
||
Line 15: | Line 15: | ||
=How to log into the account= | =How to log into the account= | ||
− | This account does not have a password; it is accessed exclusively by | + | This account does not have a password; it is accessed exclusively by ssh using your public/private key pair. To log into the account you have to have your public key on file in the gluex account in the file /home/gluex/.ssh/authorized_keys. Contact the Software Coordinator (or any person who currently has access to the account) to have your public key added. |
Revision as of 18:36, 26 January 2014
We have a group account on the JLab CUE for gluex-related tasks that are generally helpful for the entire collaboration. The username is "gluex" and is a member of the "halld" unix group.
Uses of the gluex account
Some of these tasks are run in cron jobs. By having them in a group account we can have more than one person have access to the crontab and the scripts, and it facilitates having a standard environment, i. e., it frees individuals to change the environment in their private accounts at will and not worry about breaking public jobs.
Another task is creating the standard builds of the offline software. Since all the files are owned by the system account, indiviual users cannot inadvertently overwrite or modify these builds.
How to log into the account
This account does not have a password; it is accessed exclusively by ssh using your public/private key pair. To log into the account you have to have your public key on file in the gluex account in the file /home/gluex/.ssh/authorized_keys. Contact the Software Coordinator (or any person who currently has access to the account) to have your public key added.