Sponsored Content
Full Discussion: umask
Top Forums UNIX for Dummies Questions & Answers umask Post 31326 by bb00y on Wednesday 6th of November 2002 03:43:34 AM
Old 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

umask

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

Umask help

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

help on umask

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

umask

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

umask

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

Umask

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

umask

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

UMASK

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

Help for umask

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

Umask help!

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
OPEN(2) 							System Calls Manual							   OPEN(2)

NAME
open - open a file for reading or writing, or create a new file SYNOPSIS
#include <sys/types.h> #include <fcntl.h> int open(const char *path, int flags [, mode_t mode]) DESCRIPTION
Open opens the file path for reading and/or writing, as specified by the flags argument and returns a descriptor for that file. The flags argument may indicate the file is to be created if it does not already exist (by specifying the O_CREAT flag), in which case the file is created with mode mode as described in chmod(2) and modified by the process' umask value (see umask(2)). Path is the address of a string of ASCII characters representing a path name, terminated by a null character. The flags specified are formed by or'ing the following values O_RDONLY open for reading only O_WRONLY open for writing only O_RDWR open for reading and writing O_NONBLOCK do not block on open O_APPEND append on each write O_CREAT create file if it does not exist O_TRUNC truncate size to 0 O_EXCL error if create and file exists Opening a file with O_APPEND set causes each write on the file to be appended to the end. If O_TRUNC is specified and the file exists, the file is truncated to zero length. If O_EXCL is set with O_CREAT, then if the file already exists, the open returns an error. This can be used to implement a simple exclusive access locking mechanism. If O_EXCL is set and the last component of the pathname is a symbolic link, the open will fail even if the symbolic link points to a non-existent name. If the O_NONBLOCK flag is specified and the open call would result in the process being blocked for some reason, the open returns immediately. Upon successful completion a non-negative integer termed a file descriptor is returned. The file pointer used to mark the current position within the file is set to the beginning of the file. The new descriptor is set to remain open across execve system calls; see close(2). The system imposes a limit on the number of descriptors open simultaneously by one process. ERRORS
The named file is opened unless one or more of the following are true: [ENOTDIR] A component of the path prefix is not a directory. [ENAMETOOLONG] The path name exceeds PATH_MAX characters. [ENOENT] O_CREAT is not set and the named file does not exist. [ENOENT] A component of the path name that must exist does not exist. [EACCES] Search permission is denied for a component of the path prefix. [EACCES] The required permissions (for reading and/or writing) are denied for the named file. [EACCES] O_CREAT is specified, the file does not exist, and the directory in which it is to be created does not permit writing. [EACCES] A device to be opened for writing is physically write protected. [ELOOP] Too many symbolic links were encountered in translating the pathname. (Minix-vmd) [EISDIR] The named file is a directory, and the arguments specify it is to be opened for writing. [EROFS] The named file resides on a read-only file system, and the file is to be modified. [EMFILE] The system limit for open file descriptors per process has already been reached. [ENFILE] The system file table is full. [ENXIO] The named file is a character special or block special file, and the device associated with this special file does not exist. [ENOSPC] O_CREAT is specified, the file does not exist, and the directory in which the entry for the new file is being placed cannot be extended because there is no space left on the file system containing the directory. [ENOSPC] O_CREAT is specified, the file does not exist, and there are no free inodes on the file system on which the file is being created. [EIO] An I/O error occurred while making the directory entry or allocating the inode for O_CREAT. [EFAULT] Path points outside the process's allocated address space. [EEXIST] O_CREAT and O_EXCL were specified and the file exists. SEE ALSO
chmod(2), close(2), dup(2), fcntl(2), lseek(2), read(2), write(2), umask(2). 4th Berkeley Distribution May 14, 1986 OPEN(2)
All times are GMT -4. The time now is 11:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy