[SOLVED] umask change not taking effect

mufy · 12-28-2009, 11:01 PM

Hi Folks,

This where I'm stranded.

I have 2 Oracle users that generate .tmp files under /var/tmp. By default, the files have the permissions 644. Now, a need has arisen whereby the files created by these users have to have the permission bits as 664. Obviously, I changed the UMASK value for these users from 022 to 02. But the files are still getting created with 644 as the permission.

I tried restarting the application as I read that a relogin is required for the UMASK change to take effect. Even that hasn't helped.

Any guess(es)?

paulsm4 · 12-29-2009, 12:01 AM

1. You can confirm whether or not the "umask" is taking effect by logging in as that user and typing "umask" (which will print out the current umask value).

2. If all else fails, you can globally set "umask" in your system's /etc/profile.

3. But I think the *real* questions are:

a) are these files being created in the context of that user ... or in the context of some *other* user (for example, by one or another Oracle daemons)?

b) is it possible that context is explicitly setting its own umask (overriding the logon configuration value)?

c) is it possible that program is explicitly setting read/write/execute bits when it creates the file (*excluding* the permissions you wish)?

'Hope that helps .. PSM

mufy · 12-29-2009, 12:34 AM

This is how the files look:

Code:

-rw-r--r--   1 orauat2  dba               0 Dec 29 06:30 o0289553.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 06:30 l0289553.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 06:49 o0289557.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 06:49 l0289557.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 07:00 o0289561.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 07:00 l0289561.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 08:20 o0289551.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 08:20 l0289551.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 08:30 o0288553.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 08:30 l0288553.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 08:31 o0289552.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 08:31 l0289552.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 08:33 o0289555.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 08:33 l0289555.tmp

Moreover, it is interesting to note that there were two files generated with the required permission bits

Code:


-rw-rw-r--   1 orauat   dba               0 Dec 29 09:00 o0288552.tmp
-rw-rw-r--   1 orauat   dba               0 Dec 29 09:00 l0288552.tmp

Only to revert as shown:

Code:

-rw-r--r--   1 orauat2  dba               0 Dec 29 09:00 o0289554.tmp
-rw-r--r--   1 orauat2  dba               0 Dec 29 09:00 l0289554.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 09:00 o0291551.tmp
-rw-r--r--   1 orauat   dba               0 Dec 29 09:00 l0291551.tmp

But when I switch to one of the users, say, orauat and touch file it seems ok.

Code:

-rw-rw-r--   1 orauat   dba               0 Dec 29 09:05 test.txt

And the umask value is also fine:

Code:

op58@aixuat01[/var/tmp] $su orauat
op58@aixuat01[/var/tmp] $umask
02

mufy · 01-09-2010, 11:37 PM

Solution can be found here.