Sponsored Content
Top Forums Shell Programming and Scripting checking Permissions of file for OTHERS and GROUP Post 68624 by kduffin on Tuesday 5th of April 2005 11:34:16 PM
Old 04-06-2005
Do look at the man page. There are different ways to address perms including their octal values. I imagine that you don't want to exclude if/if not the write bit is set, so:

find / -type f -perm -o+rx

Cheers,

Keith
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

root group permissions

Hello, Another newbie here and here is my dilemma. I created an account for me on Solaris 8 and I added myself to the root group. But when I login using that account I am unable to do superuser tasks.. (add users, admintool, etc). What am I missing? Thanks in advance.. Andre (5 Replies)
Discussion started by: jacobsa
5 Replies

2. Shell Programming and Scripting

checking file's permissions and change them

Hi all, I am very new to UNIX and Shell scripting, I need to run a script to check for file's and directoires permissions and change the permissions if necessary. I appreciate your help.. Thanks (7 Replies)
Discussion started by: K-ONE
7 Replies

3. Shell Programming and Scripting

checking for permissions of a file

Hi, I have a script called check.sh. I have to pass a file as input to this script. How can I validat whether the file has read permissions or not within the script. Thanks in advance (1 Reply)
Discussion started by: sendhilmani123
1 Replies

4. Filesystems, Disks and Memory

group permissions/webserver

Hi, there is one strange situation with directory permissions that I run into every now and then, and now I face it a gain with a webserver. Situation (example): drwxrwsr-x 14 user www-data 4096 Jul 28 11:06 . drwxr-xr-x 2 www-data www-data 4096 Jul 28 11:06 subdir -rwxr-xr-x 1... (3 Replies)
Discussion started by: doozer
3 Replies

5. UNIX for Dummies Questions & Answers

checking permissions security

Can you help me to find a way to check that the level of the permissions givven to Others is not higher then the permission given to Group that is not higer from Owner permissions ? (3 Replies)
Discussion started by: ynixon
3 Replies

6. UNIX for Dummies Questions & Answers

Group permissions

Hi, I've created a user named fwadmin, group named fwadmin and made the user belong to that group. I created the user and group using the 'User Manager' in Centos. The user belongs to /etc/fw.Does this also mean that the group fwadmin belongs to /etc/fw. That is what I want. But when I... (4 Replies)
Discussion started by: anaigini45
4 Replies

7. Solaris

Group Permissions - How to tell the difference

I am a member of a few different user groups. I would like to see what the difference is.... Can anyone tell me how to look at permissions side by side ? We are using : SunOS xxxxxx 5.10 Generic_127111-09 sun4u sparc SUNW,Sun-Fire-V440 Thanks ! (10 Replies)
Discussion started by: popeye
10 Replies

8. UNIX for Dummies Questions & Answers

Root group permissions

Hi everybody, which are the root group permissions and how can I give to a user these rights? Thanks in advance. (2 Replies)
Discussion started by: bmayao
2 Replies

9. UNIX for Dummies Questions & Answers

To set different file permissions for different users of same group

Hi, If User1, User2 and User3 are in the same group. User1 should not be able to view the files of User2 and User3. But User2 and User3 should be able to view all files. How to set permission for this. Please help. Thanks, Priya. (1 Reply)
Discussion started by: banupriyat
1 Replies

10. UNIX for Advanced & Expert Users

Group permissions question

I have a user who has had an id change. His old id was xl00 his new id b000999. Both id's are in group bauser. The user now cannot access his old files even though he is in the same group and permissions seem to be ok. See below, first 2 files he can't see, second two are no problem. ... (2 Replies)
Discussion started by: dw82199
2 Replies
setacl(1)						      General Commands Manual							 setacl(1)

NAME
setacl - modify access control lists (ACLs) for files (JFS File Systems only) SYNOPSIS
acl_entries file... acl_entries acl_entries]... file... acl_file file... DESCRIPTION
For each file specified, will either replace its entire ACL, including the default ACL on a directory, or it will add, modify, or delete one or more ACL entries, including default entries on directories. The option will set the ACL to the entries specified on the command line. The option will set the ACL to the entries contained within the file acl_file. The option will delete one or more specified entries from the file's ACL. The option will add or modify one or more speci- fied ACL entries. One of the options or must be specified. If or are specified, other options are invalid. The and options may be combined, and multiple and options may be specified. For the and options, acl_entries are one or more comma separated ACL entries selected from the following list. For the option, acl_file must contain ACL entries, one to a line, selected from the same list. Default entries may only be specified for directories. indicates that characters must be typed as specified, brackets denote optional characters, and italicized characters are to be specified by the user. Choices, of which exactly one must be selected, are separated by vertical bars. operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm operm|perm For the option, acl_entries are one or more comma separated ACL entries without permissions, selected from the following list. Note that the entries for file owner, owning group, and others may not be deleted. uid gid uid gid In the above lists, the user specifies the following: perm is a permissions string composed of the characters (read), (write), and (execute), each of which may appear at most one time, in any order. The character may be specified as a placeholder. operm is the octal representation of the above permissions, with 7 representing all permissions, or and 0 representing no permissions, or uid is a login name or user ID. gid is a group name or group ID. The options have the following meanings: Normally, recalculates the group class entry so as to ensure that permissions granted in the additional ACL entries will actually be granted, and the value specified in the entry is ignored. If the option is specified, the recalculation is not performed, and the value specified in the entry is used. Set a file's ACL. All old ACL entries are removed, and replaced with the newly specified ACL. There must be exactly one entry specified for the owner of the file, exactly one entry specified for the owning group of the file, and exactly one entry specified. If the option is not specified there must also be exactly one entry specified. There may be additional ACL entries and additional ACL entries specified, but there may not be duplicate additional ACL entries with the same uid, or duplicate additional ACL entries with the same gid. If the file is a directory, default ACL entries may be specified. There may be at most one entry for the owner of the file, at most one entry for the owning group of the file, at most one entry for the file group class, and at most one entry for other users. There may be additional entries and additional entries specified, but there may not be duplicate additional entries with the same uid, or duplicate additional entries with the same gid. never recalculates the entry, regardless of whether or not the option was specified. An entry with no permissions will result in the specified uid or gid being denied access to the file. The entries need not be in order. They will be sorted by the command before being applied to the file. Add one or more new ACL entries to the file, and/or change one or more existing ACL entries on the file. If an entry already exists for a specified uid or gid, the specified permissions will replace the current permissions. If an entry does not exist for the specified uid or gid, an entry will be created. Delete one or more existing ACL entries from the file. The entries for the file owner, the owning group, and others may not be deleted from the ACL. Note that deleting an entry does not necessarily have the same effect as removing all permissions from the entry. Specifically, delet- ing an entry for a specific user would cause that user's permissions to be determined by the entry (or the owning entry, if the user is in that group). Set a file's ACL with the ACL entries contained in the file named acl_file. The same constraints on specified entries hold as with the option. The entries are not required to be in any specific order in the file specified as acl_file. The character in acl_file may be used to indicate a comment. All characters, starting with the until the end of the line, will be ignored. Note that if the acl_file has been created as the output of the command, any effective permissions, which will have been written with a preceding will also be ignored. When the command is used, it may result in changes to the file permission bits. When the ACL entry for the file owner is changed, the file owner permission bits will be modified. When the ACL entry is changed, the file other permission bits will be modified. When additional ACL entries and/or any ACL entries are set or modified, the file group permission bits will be modified to reflect the maximum permissions allowed by the additional user entries and all the group entries. If an ACL contains no additional or additional entries, the permissions in the entry for the object owning group and the entry must be the same. Therefore, if the option is specified and results in no additional entries and no additional entries, the entry permissions will be set equal to the permissions of the owning group entry. This happens regardless of whether or not the option was specified. A directory may contain ACL entries. If a file is created in a directory which contains ACL entries, the entries will be added to the newly created file. Note that the default permissions specified for the file owner, file owning group, and others, will be constrained by the umask and the mode specified in the file creation call. If an ACL contains no additional or additional entries and a entry is specified for the object owning group, then a entry must also be specified, and the permissions in the entry for the object owning group and the permissions for the entry must be the same. This command may be executed on a file system that does not support ACLs, to set the permissions for the three base entries for the file owner, file owning group, and others. Additional entries and entries will not be allowed in this case. EXAMPLES
To add one ACL entry to file giving user read permission only, type: If an entry for user already exists, this command will set the permissions in that entry to To replace the entire ACL for file adding entries for users and allowing read/write access, an entry for the file owner allowing all access, an entry for the file group allowing read access only, and an entry for others disallowing all access, type: Note that following this command, the file permission bits would be set to Even though the file owning group has only read permission, the maximum permissions available to all additional ACL entries, and all ACL entries, are read and write, since the two additional entries both specify these permissions. To set the same ACL on file as in the above example, using the option, type: with file edited to contain: Because the option was not specified, no entry was needed. If a entry had been present it would have been ignored. FILES
user IDs group IDs SEE ALSO
acl(2), aclsort(3C), chmod(1), getacl(1), ls(1). setacl(1)
All times are GMT -4. The time now is 06:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy