Try setting the setgid bit on the directory's entry to the desired group;
Is this what you were out for?
This works on some systems on some file systems; it won't work on OS X nor on openBSD.
According to the standards, the group ID on a newly created file is either set to the group ID of the containing directory or to the effective group ID of the creating process. (Historically, BSD based systems used the group ID of the containing directory and System V based systems used the effective group ID of the creating process. Solaris systems used the set-GID bit on a directory to allow users to choose the behavior they wanted.) The Linux open(2) man page says that Linux systems sometimes mimic the Solaris behavior depending on the file system type and mount options used when the file system was mounted.
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 =... (1 Reply)
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)
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)
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)
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)
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)
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)
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
mkdir
MKDIR(2) Linux Programmer's Manual MKDIR(2)NAME
mkdir - create a directory
SYNOPSIS
#include <sys/stat.h>
#include <sys/types.h>
int mkdir(const char *pathname, mode_t mode);
DESCRIPTION
mkdir() attempts to create a directory named pathname.
The argument mode specifies the permissions to use. It is modified by the process's umask in the usual way: the permissions of the created
directory are (mode & ~umask & 0777). Other mode bits of the created directory depend on the operating system. For Linux, see below.
The newly created directory will be owned by the effective user ID of the process. If the directory containing the file has the set-group-
ID bit set, or if the file system is mounted with BSD group semantics (mount -o bsdgroups or, synonymously mount -o grpid), the new direc-
tory will inherit the group ownership from its parent; otherwise it will be owned by the effective group ID of the process.
If the parent directory has the set-group-ID bit set then so will the newly created directory.
RETURN VALUE
mkdir() returns zero on success, or -1 if an error occurred (in which case, errno is set appropriately).
ERRORS
EACCES The parent directory does not allow write permission to the process, or one of the directories in pathname did not allow search per-
mission. (See also path_resolution(7).)
EEXIST pathname already exists (not necessarily as a directory). This includes the case where pathname is a symbolic link, dangling or
not.
EFAULT pathname points outside your accessible address space.
ELOOP Too many symbolic links were encountered in resolving pathname.
ENAMETOOLONG
pathname was too long.
ENOENT A directory component in pathname does not exist or is a dangling symbolic link.
ENOMEM Insufficient kernel memory was available.
ENOSPC The device containing pathname has no room for the new directory.
ENOSPC The new directory cannot be created because the user's disk quota is exhausted.
ENOTDIR
A component used as a directory in pathname is not, in fact, a directory.
EPERM The file system containing pathname does not support the creation of directories.
EROFS pathname refers to a file on a read-only file system.
CONFORMING TO
SVr4, BSD, POSIX.1-2001.
NOTES
Under Linux apart from the permission bits, only the S_ISVTX mode bit is honored. That is, under Linux the created directory actually gets
mode (mode & ~umask & 01777). See also stat(2).
There are many infelicities in the protocol underlying NFS. Some of these affect mkdir().
SEE ALSO mkdir(1), chmod(2), chown(2), mkdirat(2), mknod(2), mount(2), rmdir(2), stat(2), umask(2), unlink(2), path_resolution(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 2008-05-13 MKDIR(2)