Difference between revisions of "MAS user setup"
(→Setting up the user's environment) |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 20: | Line 20: | ||
# MCE/MAS | # MCE/MAS | ||
+ | umask 002 | ||
eval `/usr/mce/bin/mas_var -s` | eval `/usr/mce/bin/mas_var -s` | ||
− | |||
== The old way == | == The old way == | ||
Line 42: | Line 42: | ||
---- | ---- | ||
Up to [[ MAS ]] | Up to [[ MAS ]] | ||
+ | |||
+ | [[Category:MAS]] |
Latest revision as of 16:25, 30 August 2016
Care must be taken when adding new users in order that
- the new user can access the MAS binaries, scripts, and IDL projects
- the new user's actions do not interfere with other users of the system
Adding a user
This can be done from the graphical manager, but since you're here you might as well use these commands:
MCE_USER=mce sudo useradd -m -g $MCE_USER -s /bin/bash new_user sudo passwd new_user
Note that the primary group of the user should be the "mce" group. This is so that temporary files can be overwritten by other users. If you want to use another username as the main MCE user, that should be fine. Adjust MCE_USER as necessary.
Setting up the user's environment
Using mas_var
mas_var is good at figuring out what your paths should be. Assuming that MAS has been installed into /usr/mce, add the following to .bashrc:
# MCE/MAS umask 002 eval `/usr/mce/bin/mas_var -s`
The old way
Before mas_var, those paths were more or less hard-coded and you needed something like the following.
Add the following lines at the end of the .bashrc file:
# MAS! umask 002 source /usr/mce/mce_script/template/mas_env.bash
MAS/IDL users will need to add $MAS_IDL/mas to their path, e.g.
IDL_PATH="<IDL_DEFAULT>:$MAS_IDL/mas"
For additional command-line functionality, engineering users may also want to add
source $MAS_SCRIPT/mas_library.bash source $MAS_TEMPLATE/mas_aliases.bash
Up to MAS