RE: [SLE] permissions problem - Linux question
What can I do to make the all new files inherit 777 perm's and/or have all new files created inherit a specific group? Both users need to be able to completely interact with files regardless who creates them.
Files are created according to what "umask" is set to, "man umask" and....
Thanks Sid. Use umask 000 on the dir and all new files created get rw-rw-rw- perm's, but after the user logs out and back in all subsequent files get rw-r--r-- perm's. How do you make the umask setting permanent? Thank you, ~James
On Friday 21 October 2005 17:49, James D. Parra wrote:
What can I do to make the all new files inherit 777 perm's and/or have all new files created inherit a specific group? Both users need to be able to completely interact with files regardless who creates them.
Files are created according to what "umask" is set to, "man umask" and....
Thanks Sid. Use umask 000 on the dir and all new files created get rw-rw-rw- perm's, but after the user logs out and back in all subsequent files get rw-r--r-- perm's. How do you make the umask setting permanent?
Thank you,
~James HI James,
The way to do this is to put the setting umask 000 in the users initialization file. The .bashrc for example. I have not seen the start of this thread so I don't know the reasoning behind this. Just be aware that this is a huge security hole as it allows all users to modify this users files. Phil
Phil, On Friday 21 October 2005 19:13, Phil Savoie wrote:
On Friday 21 October 2005 17:49, James D. Parra wrote:
...
Thanks Sid. Use umask 000 on the dir and all new files created get rw-rw-rw- perm's, but after the user logs out and back in all subsequent files get rw-r--r-- perm's. How do you make the umask setting permanent?
...
The way to do this is to put the setting umask 000 in the users initialization file. The .bashrc for example. I have not seen the start of this thread so I don't know the reasoning behind this. Just be aware that this is a huge security hole as it allows all users to modify this users files.
If you set the umask in .bashrc, you will prevent changes make within a shell from being propagated to sub-processes in cases where those sub-processes are created to run shell scripts. This would have the confusing effect of allowing binary programs to see the same umask as the shell that launched them, while giving the one from .bashrc to sub-processes running shell scripts.
Phil
Randall Schulz
James, On Friday 21 October 2005 14:49, James D. Parra wrote:
...
Files are created according to what "umask" is set to, "man umask" and....
Thanks Sid. Use umask 000 on the dir and all new files created get rw-rw-rw- perm's, but after the user logs out and back in all subsequent files get rw-r--r-- perm's. How do you make the umask setting permanent?
Using a umask "on a directory" is not how it works. Each process has its own umask value and it is passed on to child processes (as are many process parameters, such as the environment variables) when the process forks. As for making the umask "permanent," you should set it in your .bash_profile or .login (assuming you use BASH--other shells have comparable mechanisms).
Thank you,
~James
Randall Schulz
participants (3)
-
James D. Parra -
Phil Savoie -
Randall R Schulz