11-06-2002
umask
in this unix book that i have, it says:
the statement:
filedes = open(pathname, O_CREAT, mode);
is actually
filedes = open(pathname, O_CREAT, (~mask)&mode); /* ~ is the negation symbol */
like it's doing some type of masking.
for example,
fd = open("newfile", O_CREAT, 0644);
will actually given the mode of 0640.
how did it come up with that? what value does it mask to my mode set to come up with 0640?
why is it doing that?
thanks
Last edited by bb00y; 11-06-2002 at 04:51 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
the umask on solaris must return 022 or 0022
wich one is correct and why?
thanks,
pa (2 Replies)
Discussion started by: rsh
2 Replies
2. AIX
I changed the umask in /etc/security/user to 027.
I changed the umask in /etc/profile to 027.
My current shell is ksh.
My .profile doesn't make any changes to umask or call other scripts that change umask.
Running AIX 5.3
I still get a umask of 022 instead of the expected 027. I have no... (1 Reply)
Discussion started by: x96riley3
1 Replies
3. Linux
hai guys ,
i am having problem in getting the knowledge about umask.
actually when i am putting command as umask some value is coming like 0022 by defalut.
we can change its value also.
but the main thing is thye file permisiion actually depends upon umask.how is it depends upon umask i want to... (6 Replies)
Discussion started by: suvendu4urs
6 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have a doubt on the umask values.
Why is the UMASK value is different from file and directory?
Suppose if the umask value is 0022. The file permissions for a newly created file is 644 and the file permissions for a newly created directory is 755.
My doubt is why can't it be the... (1 Reply)
Discussion started by: praveen_b744
1 Replies
5. Solaris
Due to urgent requirement to resolve some permission issues , I wish
to set solaris 8 server so that any file written is on 777 .
I guess need to set umask , how to set it ?? (7 Replies)
Discussion started by: falcon16
7 Replies
6. UNIX for Dummies Questions & Answers
I need to set a umask of 022 for my ssh sessions, or within my profile.
I have set the umask in both bash_profile and bashrc.
and when i run umask i get 0022 but when i create a file i get,
# touch test.txt
# ls -l test.txt
-rw------- 1 root root 0 Apr 26 12:25 test.txt
it seems like... (1 Reply)
Discussion started by: felix001
1 Replies
7. UNIX for Advanced & Expert Users
Hi,
Please, let me know how the umask is working? As per my understanding is aprt from subtracting from 666/777, logical gate operation is performing.
Ex: If I set uname 011, it gave the permission like 666 for file. Request you to explain which gate's operation performed.
$uname 011... (4 Replies)
Discussion started by: Nagapandi
4 Replies
8. AIX
How do I change the umask for a NIS user?
Thanks
steve (1 Reply)
Discussion started by: steve.lavoie
1 Replies
9. Shell Programming and Scripting
Hi,
I want to set umask value only for vi editor.
If I create new file using vi editor, then automatic permission should be 777.
I want to set umask 000.
Please help me.
Thanks in advance (2 Replies)
Discussion started by: mnmonu
2 Replies
10. UNIX for Dummies Questions & Answers
Hi guys,
I want all new files and directories created, or copy file give this permisson "rwxrwx---", with chmod i do this with octal value "770". If i execute "umask 770" the permissons is not the same with new or copy file. How can i configure this command? I do not understand the "man... (1 Reply)
Discussion started by: Xedrox
1 Replies
LEARN ABOUT SUSE
sem_open
SEM_OPEN(3) Linux Programmer's Manual SEM_OPEN(3)
NAME
sem_open - initialize and open a named semaphore
SYNOPSIS
#include <fcntl.h> /* For O_* constants */
#include <sys/stat.h> /* For mode constants */
#include <semaphore.h>
sem_t *sem_open(const char *name, int oflag);
sem_t *sem_open(const char *name, int oflag,
mode_t mode, unsigned int value);
Link with -lrt or -pthread.
DESCRIPTION
sem_open() creates a new POSIX semaphore or opens an existing semaphore. The semaphore is identified by name. For details of the con-
struction of name, see sem_overview(7).
The oflag argument specifies flags that control the operation of the call. (Definitions of the flags values can be obtained by including
<fcntl.h>.) If O_CREAT is specified in oflag, then the semaphore is created if it does not already exist. The owner (user ID) of the sem-
aphore is set to the effective user ID of the calling process. The group ownership (group ID) is set to the effective group ID of the
calling process. If both O_CREAT and O_EXCL are specified in oflag, then an error is returned if a semaphore with the given name already
exists.
If O_CREAT is specified in oflag, then two additional arguments must be supplied. The mode argument specifies the permissions to be placed
on the new semaphore, as for open(2). (Symbolic definitions for the permissions bits can be obtained by including <sys/stat.h>.) The per-
missions settings are masked against the process umask. Both read and write permission should be granted to each class of user that will
access the semaphore. The value argument specifies the initial value for the new semaphore. If O_CREAT is specified, and a semaphore with
the given name already exists, then mode and value are ignored.
RETURN VALUE
On success, sem_open() returns the address of the new semaphore; this address is used when calling other semaphore-related functions. On
error, sem_open() returns SEM_FAILED, with errno set to indicate the error.
ERRORS
EACCES The semaphore exists, but the caller does not have permission to open it.
EEXIST Both O_CREAT and O_EXCL were specified in oflag, but a semaphore with this name already exists.
EINVAL value was greater than SEM_VALUE_MAX.
EINVAL name consists of just "/", followed by no other characters.
EMFILE The process already has the maximum number of files and open.
ENAMETOOLONG
name was too long.
ENFILE The system limit on the total number of open files has been reached.
ENOENT The O_CREAT flag was not specified in oflag and no semaphore with this name exists; or, O_CREAT was specified, but name wasn't well
formed.
ENOMEM Insufficient memory.
CONFORMING TO
POSIX.1-2001.
SEE ALSO
sem_close(3), sem_getvalue(3), sem_post(3), sem_unlink(3), sem_wait(3), sem_overview(7)
COLOPHON
This page is part of release 3.25 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 2009-02-20 SEM_OPEN(3)