Hi folks,
I'm facing the following problem:
I got a user let's say "admin" with standard group "users".
Then I got another user " with the same standard group.
I set umask for user admin so that all files being created by that users become writable for the group "users" by default.
However there's a certain binary being executed by user admin that creates a complex directory structure as well as lots of files within that structure.
Problem is that here the umask setting is being completely ignored. Everything that's being created by that binary is NOT writable by group "users".
e.g.:
Any idea what's happening here and how we could solve this issue ??
Regards,
Thomas
I'm facing the following problem:
I got a user let's say "admin" with standard group "users".
Then I got another user " with the same standard group.
I set umask for user admin so that all files being created by that users become writable for the group "users" by default.
However there's a certain binary being executed by user admin that creates a complex directory structure as well as lots of files within that structure.
Problem is that here the umask setting is being completely ignored. Everything that's being created by that binary is NOT writable by group "users".
e.g.:
Code:
> touch testfile
> ls -all testfile
-rw-rw-rw- 1 admin users 9216 Mar 17 06:38 testfile
Code:
> binary.file (being executed)
> ls -all file-being-created-by-binary-file.txt
-rw-r--r-- 1 admin users 9216 Mar 17 06:38 file-being-created-by-binary-file.txt
Any idea what's happening here and how we could solve this issue ??
Regards,
Thomas