TWiki> LHCb Web>LHCbOnline>Operator_accounts (revision 4)EditAttachPDF
The following list of operator accounts were created in the Online cluster:
AccountSorted ascending Group
calo_oper calo
muon_oper muon
ot_oper ot
rich_oper rich
st_oper st
tfc_oper online
trg_oper trg
velo_oper velo

The purpose of these accounts is to run processes that can be controlled by multiple users. For software installation there are two possibilities: install everything as the group operator or install as a normal user make sure the necessary permissions are given for your group.

The login is disabled for all operator accounts on Linux/Windows. Please find below usage examples on both platforms:


Starting tasks
There are two possibilities for starting a task as the group operator:

  • Using the runas command. Example:

1. Open a windows shell:

    Press start->run
    Type "cmd" and hit enter
2. Start the application:
    runas /user:<operator username>@LHCB <application>

  • Using the impersonator application command.
This is a utility application that allows an interface to the runas windows executable. It allows using a graphical interface for starting application, allows saving application parameters, saves the operator passwords. It should be the default way to use operator accounts. To start impersonator press:
start->programs ->impersonator 

Terminating tasks
For terminating tasks the taskmgr or the tasklist, taskkill utilities can be used:

1. Open a windows shell:

    Press start->run
    Type "cmd" and hit enter
2. Use the windows command line utilities tasklist and taskkill. Example:
   runas /user:<operator username>@LHCB tasklist -V # prints all user tasks and pids
   runas /user:<operator username>@LHCB taskkill /PID <task pid>


On Linux, two utilities called
are provided for starting and stopping services.
Starting Tasks
Assuming that a user named calouser exists in the calo group, and needs to run the event builder under the service account, the following command line should be used.
runas calo_oper /bin/bash ./
Executing this line causes the following to happen:
  • The utility checks if calo_oper is defined as a service account in /etc/serviceaccounts. If not, it aborts.
  • The utility checks if calo_oper is in the same group as the user executing the command (calo in this case). If not, it aborts.
  • The utility executes the program specified by the second argument, with all following arguments given as arguments to the program.
In this case, ./ is an argument to /bin/bash, which is the program that is started. In this way shell scripts may be run.

Stopping tasks
For stopping tasks, use the killas command in the exact same way as you would use kill. For example if a user named calouser, who is a member of the calo group calls:
killas -9 9123 9124 9135
The processes 9123, 9124, 9135 will be killed by sending SIGKILL (-9) only if:
  • The processes are owned by an account that is listed in /etc/serviceaccounts (in this case, calo_oper)
  • The account that owns these processes is a member of the calo group

Note: An extended version of the task manager was installed on all windows machines in the pit to extend the functionality of the normal taskmgr. -- RaduStoica - 21 Sep 2007

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2007-09-26 - SaiSuman
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback