12-07-2009
Hi.
This is from the chown manpage (AIX, but the same holds true for any system - I would hope!)
Quote:
Only the root user can change the owner of a file. You can change the group of a file only if you are a root user or if you own the
file. If you own the file but are not a root user, you can change the group only to a group of which you are a member.
Hope this helps!
10 More Discussions You Might Find Interesting
1. Solaris
Help......
I am running a 420R w/sol 8 and I am trying to install sun's monitoring software srs netconnect. I have installed it on 6 other boxes with no problem.
Installation failed with the message:
## Installing part 1 of 1.
/etc/opt/SUNWsrspx/CustomerCert.pem... (6 Replies)
Discussion started by: finster
6 Replies
2. UNIX for Dummies Questions & Answers
hi
currently i am migrating some directories over to a new server. is there any command (rcp or ftp or anything) for me to use without changing the ownership and permission of the directory?
i am copying some directories from unix machine to linux machine. what is the exact command?
thanks... (2 Replies)
Discussion started by: legato
2 Replies
3. UNIX for Advanced & Expert Users
Hi everyone,
Need help with an issue. The group ownership of files on my Solaris system is getting changed automatically. Could someone tell me the reason why? And how could I correct it? One more info- everytime the ownership changes, it changes to "x".
Thanks :confused: (1 Reply)
Discussion started by: top_gun
1 Replies
4. Red Hat
Hi,
I am using redhat AS 3. Recently, I was asked to implement a security control on the OS: to change ownership of /var/log/wtmp to root:sys and permission to 600. However, when I made the change and reboot the machine, everything was reverted. How come? Please help.
The following is the... (1 Reply)
Discussion started by: voa2mp3
1 Replies
5. UNIX for Dummies Questions & Answers
how would i change ownership of file1 so the user NATE gets ownership of the file? (1 Reply)
Discussion started by: trob
1 Replies
6. UNIX for Advanced & Expert Users
Folks,
I have a problem with a particular file, that seems to have some kind of lock on it, that takes around 1 hour approx to timeout. I have used lsof and nothing has an open file handle on it, yet I cannot open it. My user/group owns the file and I can create edit/delete files in... (6 Replies)
Discussion started by: scottrus
6 Replies
7. Shell Programming and Scripting
I found this search and replace method on another site:
find . -type f -print0 | xargs -0 sed -i 's/find/replace/g'
It worked fine except for the fact that it changed ownership on all the files it went through. I discovered that when my site web server suddenly couldn't serve the pages it had... (10 Replies)
Discussion started by: dheian
10 Replies
8. Shell Programming and Scripting
accidentally i have changed ownership of a directory,subdirectory and files wil below command. I want to the change ownership back as same as in same directory on another server. How can i do it?
chown -R user:group /u01
is there any simple script? it is really an urgent need.. (2 Replies)
Discussion started by: johnveslin
2 Replies
9. Solaris
Hi ,
on my Solaris 10 machine user's home directory ownership is being changed automatically to their UID. can any one please tell me whats the reason behind it .
users are there in /etc/passwd file . /etc/shadow file is also there along with nssswitch.conf file and there is no changes made to... (5 Replies)
Discussion started by: usernew
5 Replies
10. UNIX for Dummies Questions & Answers
Hi,
Here is the scenario:
This file exists, with this ownership and group:
-rw-rw-r-- 1 picard starfleet 4 Jan 3 00:33 myfile.txt
Output of the 'id' command for user picard is:
$ id picard
uid=6392(picard) gid=723(human) groups=723(human),918(starfleet)
Output... (3 Replies)
Discussion started by: Andrewkl
3 Replies
LEARN ABOUT OPENDARWIN
chown
CHOWN(8) BSD System Manager's Manual CHOWN(8)
NAME
chown -- change file owner and group
SYNOPSIS
chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
DESCRIPTION
The chown utility changes the user ID and/or the group ID of the specified files. Symbolic links named by arguments are silently left
unchanged unless -h is used.
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.)
-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 user ID and/or the group ID for the file hierarchies rooted in the files instead of just the files themselves.
-f Don't report any failure to change file owner or group, nor modify the exit status to reflect such failures.
-h If the file is a symbolic link, change the user ID and/or the group ID of the link itself.
-v Cause chown to be verbose, showing files as the owner is modified.
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.
The owner and group operands are both optional, however, one must be specified. If the group operand is specified, it must be preceded by a
colon (``:'') character.
The owner may be either a numeric user ID or a user name. If a user name is also a numeric user ID, the operand is used as a user name. The
group may be either a numeric group ID or a group name. If a group name is also a numeric group ID, the operand is used as a group name.
The ownership of a file may only be altered by a super-user for obvious security reasons.
DIAGNOSTICS
The chown utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
Previous versions of the chown utility used the dot (``.'') character to distinguish the group name. This has been changed to be a colon
(``:'') character so that user and group names may contain the dot character.
On previous versions of this system, symbolic links did not have owners.
The -v option is non-standard and its use in scripts is not recommended.
SEE ALSO
chgrp(1), find(1), chown(2), fts(3), symlink(7)
STANDARDS
The chown utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compliant.
HISTORY
A chown utility appeared in Version 1 AT&T UNIX.
BSD
March 31, 1994 BSD