07-11-2012
hah, i was wondering that myself.
I think changing the umask permission on OSX would really boggle things up.
I wish i was more familiar with unix.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Under this directory:
/var/spool/cron/crontabs/
I have the following users:
adm lp oracle root sys uucp
I believe who are able to start a cron job.
I am trying to create a cronjob under user banjob so that it can delete files older than 30 days.
How can I add user banjob... (4 Replies)
Discussion started by: simt
4 Replies
2. AIX
Trying to setup user to have the ability to delete any files (regardless of owner) in /tmp.
I've tried almost everything... the permission on the folder is drwxrwxrwt 10 bin bin, and at one point I give all the possible permission (short of root) I can give to the user, and he still can't delete... (2 Replies)
Discussion started by: cchiang12
2 Replies
3. UNIX for Dummies Questions & Answers
Hi there,
I want to change from this permission -r-xr-xr-x to -r-xr-xr-- for a set of files under unix.
Can someone help me to go-about doing this in one shot.
Cheers,
RN (2 Replies)
Discussion started by: karthickrn
2 Replies
4. Shell Programming and Scripting
Hi, all!
Is it possible to use umask and to set the file permission level as 775?
I know I can add chmod into my scripts but I just want to explore the umask option.
Thanks! (1 Reply)
Discussion started by: visio2000
1 Replies
5. Shell Programming and Scripting
Here is the sample code I'm trying to execute. I see that the permission on the file is set to 755 always I want to change it to 777. Please help me with this.
code :
#!/usr/bin/perl
use File::Path qw(make_path remove_tree);
my $path = "2010/sam";
make_path($path,{mode=>0777});
... (1 Reply)
Discussion started by: hansini
1 Replies
6. UNIX for Advanced & Expert Users
Default file system currently is 664.
I would like to get it as 774.
As other users of the same group was not able execute the file created any any user.
chmod cannot be used in my case. (Files are created and executed the programs owned by different vendors)
we know that umask is not going... (3 Replies)
Discussion started by: deepakwins
3 Replies
7. Shell Programming and Scripting
hi,
i am new in unix.......i am using bash and i want to create a user which has only some command and scripts permission.........is it possible?
thanx (1 Reply)
Discussion started by: rakeshtomar82
1 Replies
8. Shell Programming and Scripting
Hi Techies
I am stuck in a problem, I have written a script which is calling a second script which contains some command and password for quering on database. I do not want to disclose this command or specially password file. Please help..
Please have a look on directory structure and... (2 Replies)
Discussion started by: atul9806
2 Replies
9. UNIX for Dummies Questions & Answers
When am saving a file using my username in Linux environment, the file permission granted is rw-r--r--
I have to manually change the permissions using chmod command.
How do i write it to the disk as rw-rw-r while saving my file. (6 Replies)
Discussion started by: Avishek_rc1
6 Replies
10. Solaris
Hi,
Any ideas to set multiple ownership permission on a file/directory on Solaris? I need a folder to have multiple ownership on the 2 nodes servers. The 2 nodes servers require to mount a SMBFS with different user ID. Please assist. Thanks. (6 Replies)
Discussion started by: freshmeat
6 Replies
UMASK(2) Linux Programmer's Manual UMASK(2)
NAME
umask - set file mode creation mask
SYNOPSIS
#include <sys/types.h>
#include <sys/stat.h>
mode_t umask(mode_t mask);
DESCRIPTION
umask() sets the calling process's file mode creation mask (umask) to mask & 0777 (i.e., only the file permission bits of mask are used),
and returns the previous value of the mask.
The umask is used by open(2), mkdir(2), and other system calls that create files to modify the permissions placed on newly created files or
directories. Specifically, permissions in the umask are turned off from the mode argument to open(2) and mkdir(2).
The constants that should be used to specify mask are described under stat(2).
The typical default value for the process umask is S_IWGRP | S_IWOTH (octal 022). In the usual case where the mode argument to open(2) is
specified as:
S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH
(octal 0666) when creating a new file, the permissions on the resulting file will be:
S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH
(because 0666 & ~022 = 0644; i.e., rw-r--r--).
RETURN VALUE
This system call always succeeds and the previous value of the mask is returned.
CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
NOTES
A child process created via fork(2) inherits its parent's umask. The umask is left unchanged by execve(2).
The umask setting also affects the permissions assigned to POSIX IPC objects (mq_open(3), sem_open(3), shm_open(3)), FIFOs (mkfifo(3)), and
UNIX domain sockets (unix(7)) created by the process. The umask does not affect the permissions assigned to System V IPC objects created
by the process (using msgget(2), semget(2), shmget(2)).
SEE ALSO
chmod(2), mkdir(2), open(2), stat(2)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-01-09 UMASK(2)