Sponsored Content
Full Discussion: user/group
Top Forums UNIX for Dummies Questions & Answers user/group Post 16936 by Perderabo on Friday 8th of March 2002 10:46:54 AM
Old 03-08-2002
Originally files were created with the uid and gid of the process that created them. But when BSD came out they introduced multiple groups. They also decided, for some odd reason, that new files would take the gid of the directory in which they were created.

HP-UX and SunOS both copied multiple groups from BSD. But they have new files get the gid from the creating process just like System V. However they both have a secret way to obtain the old BSD behavior. If a directory has the sgid turned on, then new files are created with the same gid as the directory, not the process.

It's not easy to get that bit turned on. On HP-UX you must be root and "chmod 2755 ." did the trick. With SunOS, not only did I have to be root but also I was forced to use the mystic incantation "chmod g+s ." to turn that bit on. Once I got the bit turned on, both OS'es exhibited the BSD behavior.

So take a look at the directories permissions, I'll bet that is the answer. And I too would like to know which OS you are using. I wonder how far this concept has spread.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

User Group

I can't get a clear answer on this one... I have a Oracle user created in group 'dba' when this user touches a file the group displayed is 'sys' - why? The 'sys' group is not included in the list of secondary groups for this user. Is this standard to Oracle on Unix? (AIX) Anybody? (1 Reply)
Discussion started by: errolg
1 Replies

2. UNIX for Dummies Questions & Answers

User and Group Structure

I was asked to set up a unix system and i am at a loss. i need to know the best one for a small to medium sized business and how to go about setting up the uids and the guids for the network. what permissions i have available and such. (1 Reply)
Discussion started by: dwchapman
1 Replies

3. Solaris

Adding User to group

Hi all, I have a existing user user1 its group id dba i have created a new user named: uta and added to group dba my task for creating uta ( to ftp solaris server from /oracle/pcmia/dry1 & oracle/pcmia/dry2 and get some rdf ( database patch) and saved in one windows folder named d:\patch... (2 Replies)
Discussion started by: saurabh84g
2 Replies

4. Shell Programming and Scripting

Find all files with group read OR group write OR user write permission

I need to find all the files that have group Read or Write permission or files that have user write permission. This is what I have so far: find . -exec ls -l {} \; | awk '/-...rw..w./ {print $1 " " $3 " " $4 " " $9}' It shows me all files where group read = true, group write = true... (5 Replies)
Discussion started by: shunter63
5 Replies

5. Shell Programming and Scripting

user and its group

Hello, is there any command which can show a particular user "xyz" is belongs to how many groups thanks (3 Replies)
Discussion started by: lookinginfo
3 Replies

6. Ubuntu

Create New User with the same group nd privileges of the other user

Hi, Anyone can help me on how to duplicate privileges and group for useroradb01 to userrootdb01. I have currently using "useroradb01" and create a newly user "userrootdb01". I want both in the sames privileges and group. Please see the existing users list below; drwxr-xr-x 53 useroradb01... (0 Replies)
Discussion started by: fspalero
0 Replies

7. Debian

Group/User

Can someone help in creating a group and user. syntax to create a Group called Members. syntax to create a user called AAAA and place in to the Group Members. Thanks for your help in Advance. (3 Replies)
Discussion started by: sawyer
3 Replies

8. Shell Programming and Scripting

user without group

hi i have vert strange query.. can we add user in unix with out assigned it to any group i mean user which is having no default group or anything.. like this in /etc/passwd file new_user:::::::: Please help (2 Replies)
Discussion started by: aishsimplesweet
2 Replies

9. Linux

Nobody user group in Linux

Hi I am facing problem of taking backup of file system as username1. There are some files in system which is having group ownership as nobody. and username1 is not able to open this file and backup is failing .Even as a root user I can not open this file. File which is creating problem is ... (1 Reply)
Discussion started by: devesh123
1 Replies

10. Red Hat

User is a Part of a Group But Group Details Do Not Show the User

Hi, In the following output you can see the the user "richard" is a member on the team/group "developers": # id richard uid=10247(richard) gid=100361(developers) groups=100361(developers),10053(testers) but in the following details of the said group (developers), the said user... (3 Replies)
Discussion started by: indiansoil
3 Replies
CHMOD(1)						    BSD General Commands Manual 						  CHMOD(1)

NAME
chmod -- change file modes SYNOPSIS
chmod [-fhv] [-R [-H | -L | -P]] mode file ... DESCRIPTION
The chmod utility modifies the file mode bits of the listed files as specified by the mode operand. The options are as follows: -H If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal are not followed by default.) -L If the -R option is specified, all symbolic links are followed. -P If the -R option is specified, no symbolic links are followed. This is the default. -R Change the modes of the file hierarchies rooted in the files instead of just the files themselves. -f Do not display a diagnostic message if chmod could not modify the mode for file. -h If the file is a symbolic link, change the mode of the link itself rather than the file that the link points to. -v Cause chmod to be verbose, showing filenames as the mode is modified. If the -v flag is specified more than once, the old and new modes of the file will also be printed, in both octal and symbolic notation. The -H, -L and -P options are ignored unless the -R option is specified. In addition, these options override each other and the command's actions are determined by the last one specified. Only the owner of a file or the super-user is permitted to change the mode of a file. DIAGNOSTICS
The chmod utility exits 0 on success, and >0 if an error occurs. MODES
Modes may be absolute or symbolic. An absolute mode is an octal number constructed from the sum of one or more of the following values: 4000 (the set-user-ID-on-execution bit) Executable files with this bit set will run with effective uid set to the uid of the file owner. Directories with the set-user-id bit set will force all files and sub-directories created in them to be owned by the directory owner and not by the uid of the creating process, if the underlying file system supports this feature: see chmod(2) and the suiddir option to mount(8). 2000 (the set-group-ID-on-execution bit) Executable files with this bit set will run with effective gid set to the gid of the file owner. 1000 (the sticky bit) See chmod(2) and sticky(8). 0400 Allow read by owner. 0200 Allow write by owner. 0100 For files, allow execution by owner. For directories, allow the owner to search in the directory. 0040 Allow read by group members. 0020 Allow write by group members. 0010 For files, allow execution by group members. For directories, allow group members to search in the directory. 0004 Allow read by others. 0002 Allow write by others. 0001 For files, allow execution by others. For directories allow others to search in the directory. For example, the absolute mode that permits read, write and execute by the owner, read and execute by group members, read and execute by oth- ers, and no set-uid or set-gid behaviour is 755 (400+200+100+040+010+004+001). The symbolic mode is described by the following grammar: mode ::= clause [, clause ...] clause ::= [who ...] [action ...] action action ::= op [perm ...] who ::= a | u | g | o op ::= + | - | = perm ::= r | s | t | w | x | X | u | g | o The who symbols ``u'', ``g'', and ``o'' specify the user, group, and other parts of the mode bits, respectively. The who symbol ``a'' is equivalent to ``ugo''. The perm symbols represent the portions of the mode bits as follows: r The read bits. s The set-user-ID-on-execution and set-group-ID-on-execution bits. t The sticky bit. w The write bits. x The execute/search bits. X The execute/search bits if the file is a directory or any of the execute/search bits are set in the original (unmodified) mode. Operations with the perm symbol ``X'' are only meaningful in conjunction with the op symbol ``+'', and are ignored in all other cases. u The user permission bits in the original mode of the file. g The group permission bits in the original mode of the file. o The other permission bits in the original mode of the file. The op symbols represent the operation performed, as follows: + If no value is supplied for perm, the ``+'' operation has no effect. If no value is supplied for who, each permission bit specified in perm, for which the corresponding bit in the file mode creation mask is clear, is set. Otherwise, the mode bits represented by the specified who and perm values are set. - If no value is supplied for perm, the ``-'' operation has no effect. If no value is supplied for who, each permission bit specified in perm, for which the corresponding bit in the file mode creation mask is clear, is cleared. Otherwise, the mode bits represented by the specified who and perm values are cleared. = The mode bits specified by the who value are cleared, or, if no who value is specified, the owner, group and other mode bits are cleared. Then, if no value is supplied for who, each permission bit specified in perm, for which the corresponding bit in the file mode creation mask is clear, is set. Otherwise, the mode bits represented by the specified who and perm values are set. Each clause specifies one or more operations to be performed on the mode bits, and each operation is applied to the mode bits in the order specified. Operations upon the other permissions only (specified by the symbol ``o'' by itself), in combination with the perm symbols ``s'' or ``t'', are ignored. EXAMPLES
644 make a file readable by anyone and writable by the owner only. go-w deny write permission to group and others. =rw,+X set the read and write permissions to the usual defaults, but retain any execute permissions that are currently set. +X make a directory or file searchable/executable by everyone if it is already searchable/executable by anyone. 755 u=rwx,go=rx u=rwx,go=u-w make a file readable/executable by everyone and writable by the owner only. go= clear all mode bits for group and others. g=u-w set the group bits equal to the user bits, but clear the group write bit. BUGS
There's no perm option for the naughty bits. COMPATIBILITY
The -v option is non-standard and its use in scripts is not recommended. SEE ALSO
chflags(1), install(1), chmod(2), stat(2), umask(2), fts(3), setmode(3), symlink(7), chown(8), mount(8), sticky(8) STANDARDS
The chmod utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible with the exception of the perm symbol ``t'' which is not included in that standard. HISTORY
A chmod command appeared in Version 1 AT&T UNIX. BSD
March 31, 1994 BSD
All times are GMT -4. The time now is 01:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy