I tried something similar but some other scripts act after that.
This is what I did:
[root@gridit002 exp_soft]# cat /etc/profile.d/umask.sh
case `whoami` in
*sgm*)
echo "Now setting UMASK"
umask 002
umask
esac
But...
[root@gridit002 exp_soft]# su - dteamsgm001
Now setting UMASK
0002
[dteamsgm001@gridit002 dteamsgm001]$ umask
0022
Do I missed something?
Thank you for the help,
Simone
Carlos Borrego Iglesias wrote:
> Yes, that's what we did! but filtering with the vo's that have pool
> accounts
>
> =========================================================================
> Carlos Borrego Iglesias PIC (Port d'Informació Científica)
> tel: +34 93 581 3322 Campus UAB - Edifici D
> e-mail: [log in to unmask] E-08193 Bellaterra
> =========================================================================
>
> Avis - Aviso - Legal Notice: http://www.ifae.es/legal.html
>
>
> On Tue, 19 Jun 2007, Maarten Litmaath wrote:
>
>> Carlos Borrego Iglesias wrote:
>>
>>> Hello,
>>> At pic we have changed the mask for the pool accounts locally. Perhaps
>>> it's better if the site does it since the sgm user (for example) doesn't
>>> know if the site has pools of users for the special roles.
>> Did you add a script to /etc/profile.d for that?
>> Something like this:
>>
>> case `whoami` in
>> *sgm*)
>> umask 002
>> esac
>>
>> That might be best for the time being.
>>
|