Problem with umask

[Felipe Rodriguez_1]

When I sign on with root, the mask is set at 027.

When I sign on as a particular user, the mask is set at 002.

I can't find the setting in either profile file, or any scripts that may be running out of the profile files that could be affecting this.

Help!

[Calandrello]

Friend
to configure umask always and used the /etc/profile archive or .profile of user. therefore umask and relative to user and to all does not scheme.

[Jaime Bolanos Rojas.]

Hola Felipe!

Somebody got same issue before, please take a look at this old thread for reference:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1042248

Regards,

Jaime.

[Felipe Rodriguez_1]

I checked /etc/profile and ~/.profile

No umask setting in either.

I also checked for scripts running out of the profiles and found none.

My question is: Where is the setting coming from if not from these files?

From the thread suggested by Jaime, I see something about "source scripts". can you elaborate a little? I'm (obviously) not too knowledgeable (yet).

[Frank de Vries]

Look at our /etc/profile
and the user .profile or shell
dependent profile such as .khrc or .cshrc

Also do you log in with reflectionX ,
then check your .dtprofile as well

good luck

[Peter Godron]

Felipe,
don't forget to check the shell logins (/etc/*csh*, /etc/.login,~/.cshrc)

[James R. Ferguson]

Hi:

You asked about "sourcing".

Sourcing is Unix-speak for reading a file within a script to add variables and/or provide settings like working directory's and umasks.

To source (read) you do:

...
. file_to_source

Note that the 'file_to_source' is preceeded by a dot ("."); followed by a whitespace (blank or tab) character; and then the file to be read.

In this fashion, no new shell runs, but the actions specified in the 'file_to_source' are applied to the *current* environment.

Hence, look for "dot-space-filename" syntax in the profiles.

Regards!

...JRF...