12-04-2006
100% ownership to files
ok. this is a bit complicated.
i have a manager here who wants me to give another user access to all the files he owns. he wants this other user to have the same rights has he does.
the problem has been that whenever the manager creates a new file the permissions on the files created automatically grants the manager, the owner of the file, full read and write access but denies write and execute to everyone else, including the manager's group.
now, this other user belongs to the managers group. and i've had to manually issue a chmod -R g+w on new directories/files each time the user calls in to complain about getting permission denied. how can i deal with this so this other user automatically gets access to the files that his manager creates? i'll reiterate that he does belong to the same group as the manager.
this is SunSolaris box. i know about the umask but i'm not sure where to insert it and in which file.
any help is appreciated.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I change ownership of a directory and all of it's files without changing permissions? (1 Reply)
Discussion started by: mborin
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
While changing ownerships from the root on a server i'm managing, i typed chown -R username:users * and it changed all ownership to username. Can someone tell me if there is someway I can set things back the way they were before? I can't even su username from the root. Am I going to just... (4 Replies)
Discussion started by: szhu
4 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have a problem with a Unix server we do not adminster but have an application running on.
The problem is that overnight, files in the /user4/work directory revert to root ownership. This causes problems as we cannot process the files.
1) What would be causing files to revert to root... (1 Reply)
Discussion started by: canman
1 Replies
4. Linux
all the files and directories in my system are owned by root only.i try to(from root loggin) change the permission on the file but not permitted.can any one help to fix my problem .also while installing any software always error occur like no makefile available (1 Reply)
Discussion started by: jop
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I need a command that to copy files from others and to keep files' ownership.
Example: I copy file.txt from users "abc" to my local, and file.txt is own by user "abc" in local.
Thanks in advance! (3 Replies)
Discussion started by: need_help
3 Replies
6. UNIX for Dummies Questions & Answers
So tried:
cp -r -p test1/ user@machine:///srv/www/vhosts/domain.co.uk/httpdocs/backup/
but this didn't work either :(
Anyone able to help with this?
Many thanks
Mr M (3 Replies)
Discussion started by: misterm
3 Replies
7. UNIX for Dummies Questions & Answers
I am in the process of learning how to do system administration (just on my own Linux machine) and have been working with the find command. One of the things I tried was
find / -nouser -o -nogroup
I redirected the output of my find query into a text file, and when I did a wc -l on it, it... (1 Reply)
Discussion started by: kermit
1 Replies
8. UNIX for Dummies Questions & Answers
When I checked to see who or what owns the files in my bin directory I noticed that some were owned by root while many others were owned by bin.
Should I be concerned that there are files in this directory owned by bin or is bin the same as root as it pertains to limiting access to the files in... (3 Replies)
Discussion started by: j490428
3 Replies
9. UNIX for Advanced & Expert Users
Hi Experts,
I have create a new user with uid and gid as 0 in SuSE-11 Server. After that all the files having root owner ship are showing as new user name as owner. If I login as root, and type 'id' command, it also shows the new user.
Sample output from my server.
host:~ # id
uid=0(test)... (4 Replies)
Discussion started by: vipinable
4 Replies
10. Shell Programming and Scripting
Hi All,
I wanted to check the files ownership and permission based on the path given it as arguments thru script.
I was able to get the required command using ls but i would like this command to put in a script and check the file ownership against the what it needs to be and report back if... (12 Replies)
Discussion started by: Optimus81
12 Replies
CHMOD(1) FSF CHMOD(1)
NAME
chmod - change file access permissions
SYNOPSIS
chmod [OPTION]... MODE[,MODE]... FILE...
chmod [OPTION]... OCTAL-MODE FILE...
chmod [OPTION]... --reference=RFILE FILE...
DESCRIPTION
This manual page documents the GNU version of chmod. chmod changes the permissions of each given file according to mode, which can be
either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new permissions.
The format of a symbolic mode is `[ugoa...][[+-=][rwxXstugo...]...][,...]'. Multiple symbolic operations can be given, separated by com-
mas.
A combination of the letters `ugoa' controls which users' access to the file will be changed: the user who owns it (u), other users in the
file's group (g), other users not in the file's group (o), or all users (a). If none of these are given, the effect is as if `a' were
given, but bits that are set in the umask are not affected.
The operator `+' causes the permissions selected to be added to the existing permissions of each file; `-' causes them to be removed; and
`=' causes them to be the only permissions that the file has.
The letters `rwxXstugo' select the new permissions for the affected users: read (r), write (w), execute (or access for directories) (x),
execute only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), sticky
(t), the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group
(g), and the permissions granted to users that are in neither of the two preceding categories (o).
A numeric mode is from one to four octal digits (0-7), derived by adding up the bits with values 4, 2, and 1. Any omitted digits are
assumed to be leading zeros. The first digit selects the set user ID (4) and set group ID (2) and sticky (1) attributes. The second digit
selects permissions for the user who owns the file: read (4), write (2), and execute (1); the third selects permissions for other users in
the file's group, with the same values; and the fourth for other users not in the file's group, with the same values.
chmod never changes the permissions of symbolic links; the chmod system call cannot change their permissions. This is not a problem since
the permissions of symbolic links are never used. However, for each symbolic link listed on the command line, chmod changes the permis-
sions of the pointed-to file. In contrast, chmod ignores symbolic links encountered during recursive directory traversals.
STICKY FILES
On older Unix systems, the sticky bit caused executable files to be hoarded in swap space. This feature is not useful on modern VM sys-
tems, and the Linux kernel ignores the sticky bit on files. Other kernels may use the sticky bit on files for system-defined purposes. On
some systems, only the superuser can set the sticky bit on files.
STICKY DIRECTORIES
When the sticky bit is set on a directory, files in that directory may be unlinked or renamed only by root or their owner. Without the
sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as
/tmp, that are world-writable.
OPTIONS
Change the mode of each FILE to MODE.
-c, --changes
like verbose but report only when a change is made
-f, --silent, --quiet
suppress most error messages
-v, --verbose
output a diagnostic for every file processed
--reference=RFILE
use RFILE's mode instead of MODE values
-R, --recursive
change files and directories recursively
--help display this help and exit
--version
output version information and exit
Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxXstugo.
AUTHOR
Written by David MacKenzie.
REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>.
COPYRIGHT
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
The full documentation for chmod is maintained as a Texinfo manual. If the info and chmod programs are properly installed at your site,
the command
info chmod
should give you access to the complete manual.
chmod (coreutils) 4.5.3 February 2003 CHMOD(1)