Currently user management is done on the command line.
Adding User Accounts
Adding users is conveniently performed by invoking the script`/usr/sbin/adduser.sh.`. Example:
0 root@cl-head ~ # /usr/sbin/adduser.sh -u username -n 'real name'
This script performs all the tasks necessary for creating a new user account. There are a
number of options to it, that you can see when invoking it using the
-h flag. It reads the
/etc/qlustar/common/adduser.cf for default values.
The user ids of new accounts should be greater than 1000 to avoid a conflict with existing system accounts.
Removing User Accounts
Use the script
/usr/sbin/removeuser.sh to remove a user account from the system. Example:
0 root@cl-head ~ # removeuser.sh username
To recursively remove the user’s home-directory as well add the
0 root@cl-head ~ # removeuser.sh -r username
Managing user restrictions
In the default configuration of a Qlustar cluster, all registered users are allowed to login by ssh on the cluster nodes. If this is not wanted, it is easily possible for cluster admins to change the default behavior. Users will then be allowed to ssh only into nodes where one of their jobs is running. To activate this setting for a node, use QluMan to assign the generic property _Limit User Logins with a value yes to it.
The Qlustar shell setup supports tcsh and bash. There are global initialization files that are used in both shells, so you only have to modify one file for environment variables, aliases and path variables. The global files are:
Use this file to add or modify environment variables that are not path variables. The syntax of this file is as follows: lines beginning with a hash sign (#) and empty lines are ignored. Every other line consists of a variable name and the value for this variable separated with a space. Example: the following line sets the variable
~/.ql-envin a user’s home directory can define personal environment variables in the same manner.
Use this file to define shell aliases. It has the same syntax as the file
envdescribed above. Again, a personal
~/.ql-aliasfile can define personal aliases.
This directory contains files with a name of the form
varname.Linux. The varname is converted to upper case and specifies a ‘PATH like’ environment variable (e.g.
CLASSPATH, … ). Each line in this file is a directory to add to this environment variable. If the line begins with a ’p’ followed by a space followed by a directory, then this directory is prepended to the path variable otherwise it is appended. A user can create his/her own
~/.pathsdirectory and so can use the same mechanism.
We provide an extensible bash setup and bash is the recommended login shell. The bash startup
consists of global settings and user settings. Global settings are stored in files under
/etc/qlustar/common/skel. User settings are stored in files in the corresponding home
This file sources the other bash files. Do not modify.
This file is used for setting bash variables.
This file defines bash aliases.
You can use this file if you plan to create bash functions available to users.
~/.bashrc also sources the following user specific files which have the same meaning
as the global bash files.
We provide a similar setup for the tcsh. The following files are used:
This global tcshrc is sourced first and sources other startup files.
Use this file to set tcsh variables.
You can use this file to define tcsh aliases.
~/.tcshrc also sources the following use specific files which have the same meaning
as the global tcsh files.