Sponsored Content
Full Discussion: Access another users files
Top Forums UNIX for Dummies Questions & Answers Access another users files Post 302361850 by zaxxon on Wednesday 14th of October 2009 08:17:27 AM
Old 10-14-2009
Only root can hand over files with chown. If you are in the group that has permissions on the files and got the "r"-flag, then you can read them.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Creating USERs with restricted Access

Hi There, i need to creat USERS in UNIX with restricted access to different directories. for example user1 should have access to dir1 and dir2 user2 should have access to dir2 and dir3 Please help me (4 Replies)
Discussion started by: ramanan25
4 Replies

2. AIX

Find all users with shell access

Hi, how do I find all users currently setup with shell access. Thanks in advance. Gav (1 Reply)
Discussion started by: LionFeen
1 Replies

3. UNIX for Advanced & Expert Users

Restrict access to specific users.

Hi All! I would like to know if there is any specific way by which I can restrict access to apecific users (ip addresses). OS : Red hat linux Thanks! nua7 (6 Replies)
Discussion started by: nua7
6 Replies

4. AIX

cloning users access with different user name

Hi! this would be my first time to post here in this forums, hope you can help me with my queries. i would like to create a different user name but have the same access rights. Example: root > rootbaby. thanks (5 Replies)
Discussion started by: HPL1706
5 Replies

5. Solaris

List users who have administrative access

Hi , Could you please give me the commands for the following. 1.list users who have direct access to solaris database at os-level 2.list users who have administrative access at os-level in solaris Please also let me know how to figure out these specific users i need from a... (6 Replies)
Discussion started by: James777
6 Replies

6. UNIX for Dummies Questions & Answers

kernel giving access for multiple users to access files

hi all, i want to know y kernel is giving access for multiple users to access a file when one user may be the owner is executing that file. Because other user can manipulate that file when the other user is executing that file, it will give the unexpected result to owner . plz help me... (1 Reply)
Discussion started by: jimmyuk
1 Replies

7. HP-UX

access to .beroot for users

Hp info HP-UX tmelps04 B.11.31 U ia64 issue I created a user in his primary group is sysadmin. However when this user executes HPPI he gets shot down because he is not a super user. How do I grant the user permissions to access the beroot script? Sorry, user xxxxxx is not allowed to execute... (2 Replies)
Discussion started by: sctxms
2 Replies

8. Shell Programming and Scripting

Access rights for users - list

Hi, I would like to retrieve a list of user ids on an AIX server along with the access rights that each id has? Can someone please help me on how this can be achieved? Gayathri (3 Replies)
Discussion started by: ggayathri
3 Replies

9. Solaris

samba read write access to owner and no access to other users

Hi All, I want to configure samba share permission so that only directory creator/owner has a read and write permission and other users should not have any read/write access to that folder.Will that be possible and how can this be achieved within samba configuration. Regards, Sahil (1 Reply)
Discussion started by: sahil_shine
1 Replies

10. Solaris

How to check sudo access of other users?

Hi, I always use "sudo -U user -l" as root and it gives me list of sudo access, that person have. But on one Solaris server, I can't run it. recently only I installed latest patchset on this server. Not sure, if that changed something on this. However, sudo package is showing old one. # id -a... (1 Reply)
Discussion started by: ron323232
1 Replies
CHOWN(8)						    BSD System Manager's Manual 						  CHOWN(8)

NAME
chown -- change file owner and group SYNOPSIS
chown [-fhvx] [-R [-H | -L | -P]] owner[:group] file ... chown [-fhvx] [-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 of the specified directory trees (recursively, including their contents) and files. Beware of unintentionally matching the ``..'' hard link to the parent directory when using wildcards like ``.*''. -f Do not 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. If the -v flag is specified more than once, chown will print the filename, followed by the old and new numeric user/group ID. -x File system mount points are not traversed. 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. EXIT STATUS
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 and -x options are non-standard and their 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
February 21, 2010 BSD
All times are GMT -4. The time now is 05:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy