This page describes how write access to the KLOE online software disk can be granted to developers.
The concept of a group is used to allow write access to directories and files. The offline group use the same mechanism which is already described well in KLOE Memo #4 chapter 7.1. This page only summarizes the important issues.
For the KLOE online group the group name kloedaq has been setup on the LNF UNIX Cluster (and for the event display kloedisp). We must destinguish between using and managing the online software areas.
and then change to the new group:on HP-UX > libwho kloedaq on OSF1 > id on both > ypcat group | grep kloedaq
which actually makes a new login. The id command just displays your ownership and group ownership. Type exit to go back to your original session.> id > newgrp kloedaq > id
To allow other developers write access
to files you have created you must have
a proper umask defined:
If you call the KLOE group startup script ~kloe/group_cshrc in your ~/.(t)cshrc file then this is automatically done. If not then you can insert the following line in your startup script:> umask > umask 002
# Set group umask
if ( `id | cut -f3 -d"(" | cut -f1 -d")"` =~ "kloe[a-z]*" ) umask 002
This describes briefly, how a directroy tree must be setup to allow group development access with the group mechanism:
> newgrp kloedaq > mkdir skel > ls -ld skel drwxrwxr-x 2 wolf kloedaq 24 Mar 31 18:53 skel > chmod g+ws skel > ls -ld skel drwxrwsr-x 2 wolf kloedaq 24 Mar 31 18:53 skel
The 's' permission garanties that all newly created directories under skel will have exactly the same group ownership and permissions.
Suggestions, comments or questions? Please contact:
Wolfgang Grandegger (wolf@hpkloe01.lnf.infn.it)