08-25-2008
When you created the file, some app (example: an editor on another PC or on your unix box), writes the file for the first time and the umask value is different from your default umask. The protections persist unless you overwrite them.
apps may call umask, so that while running and creating files in your name, the protections are different.
man 2 umask
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
We have 2 users and one directory (dir). One user is admin user and other use r is operator user. who is responsible for just executing the scripts e.g. startWeblogic and stopWeblogic etc, we want to restrict this operator user in such a way that he can only execute these files and he should... (2 Replies)
Discussion started by: reldb
2 Replies
2. UNIX for Dummies Questions & Answers
Whenever I create a new file the group name is "dnn" and the file permissions are "-rw-r--r--".
How do I get it so when I create files (with vi or other programs) that the default group is "sss" and the permissions are 770?
(I am running HP-UNIX)
Thanks,
GoldFish (2 Replies)
Discussion started by: goldfish
2 Replies
3. UNIX for Dummies Questions & Answers
Please explain this strange behavior to me
bash-2.03$ ls -l abc
-rw------- 1 bashboy users 319 Sep 21 18:02 abc
bash-2.03$ ./abc
bash: ./abc: Permission denied
bash-2.03$ . abc
Successfully run
I wanted to ask how the file executes without the execute permissions when we... (3 Replies)
Discussion started by: rakeshou
3 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
I want to know differences between read,write & execute permissons given to directory.
Thanx in advance. (6 Replies)
Discussion started by: vishwasrao
6 Replies
5. IP Networking
Hi,
We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
Discussion started by: swatidas11
1 Replies
6. Solaris
Hi all.
On one workstation run Solaris 10 a simple user can to execute 'init 0' command without input (su and root password).
Example:
% init 0
%
OK
I don't understand how user can execute 'init 0' command on this workstation?
1) I checked /usr/local/etc/sudoers all lines are... (6 Replies)
Discussion started by: wolfgang
6 Replies
7. Solaris
hi all
how I can create an ftp user in solaris 10 and have read and write permission on a directory.
Thanks. (1 Reply)
Discussion started by: luisfja
1 Replies
8. Shell Programming and Scripting
I want to check access rights permissions not for 'user', not for 'group', but for 'others'.
I want to do it by system command in which i want to use 'ls -l' and 'awk' command.
I have written the following program :
#!/usr/bin/local/perl
#include <stdlib.h>
system ("ls -l | awk... (1 Reply)
Discussion started by: shubhamsachdeva
1 Replies
9. UNIX for Beginners Questions & Answers
i want to give users the ability to create write and read files in other user directory , but not to have option to delete the file after created ( sticky bit not going to work here ... ) for example :
i have user : manager with directory repository
i have user : worker1 that need to write... (4 Replies)
Discussion started by: umen
4 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.27 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)