Page History

...

• Issue training to the user on Lab 1 use. Points to make:
  • No access through middle hallway door
  • No access to stuff not part of the user's project
  • Stay out of the racks unless the user really needs access
    • High currents present
  • No reconfiguration of computers
  • No reconfiguration of the network
  • Keep the place clean
  • Point out Dataflow Lab 1 Confluence page and have the user go over it
• Introduce the user to Mike

• Create a computer account for the user

  Panel

  For the old method, see /reg/common/tools/bin/addlabuser, etc. This is obsolete as of 1/1/2012, now that we have moved to unix-admin style maintenance. However, it may still be needed for legacy set-ups. On rdsrv100, issue: /reg/common/tools/bin/addlabuser <username> Puts user in the appropriate groups, e.g., lab-users Add --superuser to add the user to the sudo list, if necessary If this fails with a 'User not found in ou=People...' message issue: /reg/common/tools/ldap-helpers/nis2ldap Retry addlabuser

  • Add the account to the u-reg-lab1 netgroup (NIS) with a request to unix-admin
• If the user is involved with RCE development (DAT, CTK, CCI, NPA, etc.):
  • Send a request to confluence_admin to add the user to the cci-confluence-editors group and get the user CCI JIRA privileges
  • Add the user to the g-npaAFS group, if necessary
    • Needed for NPA cvs/svn access, as in, e.g., ATLAS
  • Add the user to the g-cciAFS group, if necessary

    • Needed for RCE development svn access

      Code Block
      pts membership g-cci pts adduser <username> g-cci

  • Add the user to the reg-lab1YP group, if necessary

    • Needed for certain Lab 1 NFS disk operations

      Code Block
      ypgroup exam -group reg-lab1 ypgroup adduser -group reg-lab1 -user <username>

• Add the account to the reg-lab listserv e-mail list (see below)
  • Send an e-mail to listserv with subscribe reg-lab <user>@SLAC.Stanford.edu in the message body
  • Can also add the user by going to listserv

...