Sponsored Content
Top Forums UNIX for Advanced & Expert Users File group ownership changing automatically Post 92373 by Just Ice on Friday 9th of December 2005 02:37:36 PM
Old 12-09-2005
which files are created under which directory? what are the permissions of the directory the files are created in? how are the files created --- through a script, FTP upload, manually, etc.? what os and version are you running? also, post "ls -l" listing of one (or a few) of the affected files and directory ...
 

10 More Discussions You Might Find Interesting

1. Solaris

Diectory ownership ...changing

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

copy directory without changing ownership setting

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. Red Hat

changing wtmp ownership and permission

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

4. UNIX for Dummies Questions & Answers

changing ownership?

how would i change ownership of file1 so the user NATE gets ownership of the file? (1 Reply)
Discussion started by: trob
1 Replies

5. UNIX for Advanced & Expert Users

Permission denied, but user is owner and has group ownership too

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

6. UNIX for Dummies Questions & Answers

regarding changing ownership and group

i am able to change the mode using chmod and able to change permission. but i am not able to change group and ownership. getting as invalid can any one help me regarding this . (4 Replies)
Discussion started by: satheeshkr_cse
4 Replies

7. Shell Programming and Scripting

Search and replace without changing ownership

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

Changing ownership of a directory, subdirectory and files as same as in another server

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

User's Home directory ownership is changing Automatically

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

'cp' command: preserve group ownership

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
chown(1)							   User Commands							  chown(1)

NAME
chown - change file ownership SYNOPSIS
/usr/bin/chown /usr/bin/chown [-fhR] owner[:group] file... /usr/bin/chown -s [-fhR] ownersid[:groupsid] file... /usr/bin/chown -R [-f] [-H | -L | -P] owner[:group] file... /usr/bin/chown -s -R [-f] [-H | -L | -P] ownersid[:groupsid] file... /usr/xpg4/bin/chown /usr/xpg4/bin/chown [-fhR] owner[:group] file... /usr/xpg4/bin/chown -s [-fhR] ownersid[:groupsid] file... /usr/xpg4/bin/chown -R [-f] [-H | -L | -P] owner[:group] file... /usr/xpg4/bin/chown -s -R [-f] [-H | -L | -P] ownersid[:groupsid] file... ksh93 chown [-cflhmnvHLPRX] [-r file] owner[:group] file... DESCRIPTION
/usr/bin/chown and /usr/xpg4/bin/chown The chown utility sets the user ID of the file named by each file to the user ID specified by owner, and, optionally, sets the group ID to that specified by group. If chown is invoked by other than the super-user, the set-user-ID bit is cleared. Only the owner of a file (or the super-user) can change the owner of that file. The operating system has a configuration option {_POSIX_CHOWN_RESTRICTED}, to restrict ownership changes. When this option is in effect the owner of the file is prevented from changing the owner ID of the file. Only the super-user can arbitrarily change owner IDs whether or not this option is in effect. To set this configuration option, include the following line in /etc/system: set rstchown = 1 To disable this option, include the following line in /etc/system: set rstchown = 0 {_POSIX_CHOWN_RESTRICTED} is enabled by default. See system(4) and fpathconf(2). ksh93 The chown built-in in ksh93 is associated with the /bin and /usr/bin paths. It is invoked when chown is executed without a pathname prefix and the pathname search finds a /bin/chown or /usr/bin/chown executable. chown changes the ownership of each file to owner. owner can be specified as either a user name or a numeric user id. The group ownership of each file can also be changed to group by appending :group to the user name. OPTIONS
/usr/bin/chown and /usr/xpg4/bin/chown The following options are supported: -f Force. Does not report errors. -h If the file is a symbolic link, this option changes the owner of the symbolic link. Without this option, the owner of the file refer- enced by the symbolic link is changed. -H If the file specified on the command line is a symbolic link referencing a file of type directory, this option changes the owner of the directory referenced by the symbolic link and all the files in the file hierarchy below it. If a symbolic link is encountered when traversing a file hierarchy, the owner of the target file is changed, but no recursion takes place. -L If the file is a symbolic link, this option changes the owner of the file referenced by the symbolic link. If the file specified on the command line, or encountered during the traversal of the file hierarchy, is a symbolic link referencing a file of type directory, then this option changes the owner of the directory referenced by the symbolic link and all files in the file hierarchy below it. -P If the file specified on the command line or encountered during the traversal of a file hierarchy is a symbolic link, this option changes the owner of the symbolic link. This option does not follow the symbolic link to any other part of the file hierarchy. -s The owner and/or group arguments are Windows SID strings. This option requires a file system that supports storing SIDs, such as ZFS. Specifying more than one of the mutually-exclusive options -H, -L, or -P is not considered an error. The last option specified determines the behavior of chown. /usr/bin/chown The following options are supported: -R Recursive. chown descends through the directory, and any subdirectories, setting the specified ownership ID as it proceeds. When a symbolic link is encountered, the owner of the target file is changed, unless the -h or -P option is specified. However, no recursion takes place, unless the -H or -L option is specified. /usr/xpg4/bin/chown The following options are supported: -R Recursive. chown descends through the directory, and any subdirectories, setting the specified ownership ID as it proceeds. When a symbolic link is encountered, the owner of the target file is changed, unless the -h or -P option is specified. Unless the -H, -L, or -P option is specified, the -L option is used as the default mode. ksh93 The following options are supported by the ksh93 built-in chown command: -c --changes Describe only files whose ownership actually changes. -f --quiet | silent Do not report files whose ownership fails to change. -l | h --symlink Change the ownership of the symbolic links on systems that support this option. -m --map Interpret the first operand as a file that contains a map of: from_uid:from_gid to_uid:to_gid pairs. Ownership of files matching the from part of any pair is changed to the corresponding to part of the pair. The process stops at the first match for each file. Unmatched files are silently ignored. -n --show Show actions but do not execute. -r --reference=file Omit the explicit ownership operand and use the ownership of the file instead. -v --verbose Describe the changed permissions of all files. -H --metaphysical Follow symbolic links for command arguments. Otherwise do not follow symbolic links when traversing directories. -L --logical | follow Follow symbolic links when traversing directories. -P --physical | nofollow Do not follow symbolic links when traversing directories. -R --recursive Recursively change ownership of directories and their contents. -X --test Canonicalize output for testing. OPERANDS
The following operands are supported: owner[:group] A user ID and optional group ID to be assigned to file. The owner portion of this operand must be a user name from the user database or a numeric user ID. Either specifies a user ID to be given to each file named by file. If a numeric owner exists in the user database as a user name, the user ID number associated with that user name is used as the user ID. Sim- ilarly, if the group portion of this operand is present, it must be a group name from the group database or a numeric group ID. Either specifies a group ID to be given to each file. If a numeric group operand exists in the group database as a group name, the group ID number associated with that group name is used as the group ID. file A path name of a file whose user ID is to be modified. USAGE
See largefile(5) for the description of the behavior of chown when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes). EXAMPLES
Example 1 Changing Ownership of All Files in the Hierarchy The following command changes ownership of all files in the hierarchy, including symbolic links, but not the targets of the links: example% chown -R -h owner[:group] file... ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of chown: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 The utility executed successfully and all requested changes were made. >0 An error occurred. FILES
/etc/passwd System password file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/chown +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled. See NOTES. | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ /usr/xpg4/bin/chown +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWxcu4 | +-----------------------------+-----------------------------+ |CSI |Enabled. See NOTES. | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ ksh93 +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The ksh93 built-in binding to /bin and /usr/bin is Volatile. The built-in interfaces are Uncommitted. SEE ALSO
chgrp(1), chmod(1),ksh93(1), chown(2), fpathconf(2), passwd(4), system(4), attributes(5), environ(5), largefile(5), standards(5) NOTES
chown is CSI-enabled except for the owner and group names. SunOS 5.11 11 Jul 2008 chown(1)
All times are GMT -4. The time now is 08:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy