GlueX-related shared accounts on the JLab CUE
We have a set of accounts on the JLab CUE for gluex-related tasks that are generally helpful for the entire collaboration. They are all members of the "halld" unix group. The "gluex" account is for general system administration tasks and the "gxprojx" (gluex project) accounts are for large-scale computing tasks, especially those using the batch farm.
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.
Uses of the GlueX Project accounts
Mainly for submitting jobs to the batch farm, users gxproj1, 2, 3, and 4 have elevated privilege on the farm relative to normal "halld" group accounts. The offline software working group allocates these accounts for large-scale computing tasks as they arise.
|Account||Project||Contact Person||Date Assigned|
|gxproj1||Offline Monitoring||Kei Moriya||December 2014|
|gxproj2||Data Challenge 3||Mark Ito||December 2014|
|gxproj3||EventStore||Sean Dobbs||January 2015|
|gxproj4||High-Resolution FCAL Insert Studies||Ilya Larin||March 2015|
How to log into the accounts
These accounts do not have passwords; they are accessed exclusively by ssh using your public/private key pair. To log into an account you have to have your public key on file in the target account's home directory tree in the file /home/<gluex-account>/.ssh/authorized_keys. Contact the Software Coordinator (or any person who currently has access to the account of interest) to have your public key added.