Is there a way to change a unix user's default file permissions so that when he creates a file, by default permissions are 777???

Thanks!

see here for explanation.

Fred,

Look at the man page for the 'umask' command.

Careful - the umask command works to REMOVE permissions from the user's default, rather than add them.

More generally, this will acheive what you need, but consider the security implications of setting the user's default file creation permissions to 777 before you proceed.

Steve

I set umask ugo=rwx for a test user.

I then vi a test file (tree). When it's created it's not getting X, just RW.

"tree" [New file] 1 line, 5 characters
$ ls -ltr
total 672
-rw-rw-r-- 1 root sys 5296 Apr 3 06:33 ps_data
-rw-r--r-- 1 root other 5 Apr 25 12:41 speckeysd.lock
-rw------- 1 root other 310984 Apr 25 12:41 dtdbcache_:0
-rw-r--r-- 1 root other 0 Apr 25 12:41 sdtvolcheck3076
drwx------ 3 root root 244 Apr 25 12:42 smc898
-rw-rw-rw- 1 rallen cdsweb 5 May 16 12:46 tree
$ umask
00
$


When I create a file it has RW for UGO, but not X. Why isn't execute being set for UGO?

Thanks!

Files get created by Unix as 666. Then the umask get's applied. So the maximum file creation can only be -rw-rw-rw (666) minus the umask. If 000 is the umask then nothing changes. If the umask is 777, then the file becomes ----------.

It's kind of a nice feature to have files that get created as not executable. Why? Think of a virus. Think of an exe in windows. You get sent and exe in windows and it runs, period. The cool thing about unix and linux is that the virus won't be executable from the start, you have to tell it to become executable. It's really a nice security feature.

-X

Is there any way to make a file be RWX (777) by default?

It's a requirement for this server, I understand the security issues, they make perfect sense ... but this server is just used by 2 people for development and test and having files be 777 is a requirement unfortunately. I was just wondering if there is a way to make them RWX (777) by default so they don't have to do it manually.

Thanks!

Yes, there's a way. Get a windows server.

I am really curious to know what is this "requirement" that asks for every file to be executable.
"I don't want to type chmod +x script.sh every time" is really not a requirement.