Sponsored Content
Operating Systems Solaris Giving read write permission to user for specific directories and sub directories. Post 303018579 by blinkingdan on Monday 11th of June 2018 03:57:59 AM
Old 06-11-2018
Giving read write permission to user for specific directories and sub directories.

I have searched this quite a long time but couldn't find the right method for me to use. I need to assign read write permission to the user for specific directories and it's sub directories and files. I do not want to use ACL. This is for Solaris. Please help.

Last edited by blinkingdan; 06-11-2018 at 05:04 AM..
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Change permission for directories and files

Is there a way to change subdirectories permission plus the files in the subdirectories in a directory i specified without using the find command? (1 Reply)
Discussion started by: mingfei2006
1 Replies

2. Shell Programming and Scripting

Batch delete specific folder from user home directories

Hi! Need your help. How can I delete the cache folder of multiple user home directories via automatically executed shell script on a Mac OS X Server? Example: The userdata are stored on a Xsan Volume like this: /Volumes/Xsan/userdata/mike /Volumes/Xsan/userdata/peter... (2 Replies)
Discussion started by: nipodrom
2 Replies

3. Shell Programming and Scripting

Find all files with group read OR group write OR user write permission

I need to find all the files that have group Read or Write permission or files that have user write permission. This is what I have so far: find . -exec ls -l {} \; | awk '/-...rw..w./ {print $1 " " $3 " " $4 " " $9}' It shows me all files where group read = true, group write = true... (5 Replies)
Discussion started by: shunter63
5 Replies

4. Shell Programming and Scripting

Bash Script to Read & Write on different directories

Hi, root@server] df -h 121G 14G 101G 12% /home 147G 126G 14G 91% /backup We having our site files and images are storing in /backup/home/user/files/ through symbolic link created in /home directory pointing in /backup directory as following. root@server] cd /home... (1 Reply)
Discussion started by: mirfan
1 Replies

5. UNIX for Dummies Questions & Answers

How to find out in which directories a user can write?

Hi everybody, what command can show me the directories in which a certain user can write to? Kind Regards FranzB (2 Replies)
Discussion started by: FranzB
2 Replies

6. Shell Programming and Scripting

Giving write permission to multiple directories

Hi, i am having following directory structure Folder1 -> Folder2 -> Folder3 Folder4 Folder5 Now i am at top level and want to assign write permission to all the folder & files in it. i am... (3 Replies)
Discussion started by: sarbjit
3 Replies

7. UNIX for Dummies Questions & Answers

Do UNIX Permission apply to sub directories?

Hi Guys, Can you tell me if unix permissions apply to sub dirs? Dir is /home/ops/batch/files/all /home is rwxrwxrwx ops is rwxrwxrwx batch is rwxr-wr-w files is rwxrwxrwx all is rwxrwxrwx Having problems writing to all (does the userid nee to be the batch owner... (1 Reply)
Discussion started by: Grueben
1 Replies

8. UNIX for Dummies Questions & Answers

Highlight directories in path with execute permission for others

Hi all, I'm trying to make a script that takes at the most one argument and lists all directories in the path in a special format: User Group Other Filename rwx r-- r-x \ rwx r-x r-- home This is my code as it is... (1 Reply)
Discussion started by: Trinimini
1 Replies

9. AIX

Assign read write permission to the user for specific dir and it's sub dir and files in AIX

I have searched this quite a long time but couldn't find the right method for me to use. I need to assign read write permission to the user for specific directories and it's sub directories and files. I do not want to use ACL. I do not want to assign user the same group of that directories too.... (0 Replies)
Discussion started by: blinkingdan
0 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 08:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy