- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Directory permissions
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 01:31 PM
11-25-2004 01:31 PM
I am tryng to grant rwx permissions specifically to one user.
I found ACL could do the work, but when doing so (setcl) it gives the permissions to the directory but only on new files and directories. The prmissions for the older ones stay the same.
The idea is that this user can rwx on all subdirectories and files (old and new ones)
What should I do?
Thanks in advance
Nilton Medina Ygreda
IT Systems
SENATI
Lima, Per
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 01:50 PM
11-25-2004 01:50 PM
Re: Directory permissions
I'd kind of have to know what the users groups were to recommend an exact course of action.
It might be as simple as a chmod -R command -R for recursive on subdirectories.
It might be more complex. More details needed to provide better help.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2004 01:59 PM
11-25-2004 01:59 PM
Re: Directory permissions
Look at the man page of 'acl'.
//An ACL entry prefixed with d: or default:, can only occur in a directory's ACL, and it indicates that the remainder of the entry is not to be used in determining the access rights to the directory, but is instead to be applied to any files or subdirectories created in the directory//
You will need to manually set the permissions to the existing files. Use 'find /directory |xargs setacl ...' to set the permissions for the existing files/directories.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2004 05:46 AM
11-26-2004 05:46 AM
Re: Directory permissions
Well I guess giving permissions manually would be really a great job since there are 15 sub directories to include. Beisdes, The idea is to give permissions only to one user, not all the "others" so maybe chmod is not a good choice (or yes?).
The scenario goes like this
Directory structure:
/d1/s1/ABC
/d1/s1/ABC/ss1 ... /d1/s1/ABC/ss1/dsd1 ...
/d1/s1/ABC/ss2 ... /d1/s1/ABC/ss1/dsd2 ...
/d1/s1/ABC/ss3 ... /d1/s1/ABC/ss1/dsd3 ...
The instruction I used was:
# setacl -m u:userx:rwx d1/s1/ABC
The user "userx" belongs to the "users" group
After the instruction above, userx is able to rwx at "/d1/s1/ABC" but only can create new files/directories (or delete them), but cannot write or delete on the other subdirectories or files already existing.
Again, thanks in advance an thanks for your time.
Nilton Medina Ygreda
IT Systems
SENATI
Lima, PerÃ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2004 05:51 AM
11-26-2004 05:51 AM
Re: Directory permissions
Setting permissions manually is not a difficult job. Just use 'find' command as I mentioned before.
find /your_directory|xargs setacl -m u:userx:rwx
Check to see if the permissions have been set correctly.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2004 05:56 AM
11-26-2004 05:56 AM
Re: Directory permissions
Please ... wish me good luck
thanks,
Nilton
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2004 06:15 AM
11-26-2004 06:15 AM
Re: Directory permissions
You could compile a list of subdirectories.
dir *. will get a list of direcectories in a the current directory.
ls -alr | grep dr
Will get a list of directories including what you want to change.
You can process the list with awk.
ls -alr | grep dr > /tmp/filelist
cat /tmp/filelist | `{print $8}` > /tmp/file2
while read -r filename
do
chmod ### $filename
done < /tmp/file2
replace ### with the permissions you want.
Saves time.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2004 07:57 AM
11-26-2004 07:57 AM
SolutionBe VERY careful with find and chown -R!!! An accidental symbolic link might connect a current directory into another. Do this task as root and it's possible ruin the entire system. Verify exactly what files will be affected by using find without the -exec option to get a list first.
Bill Hassell, sysadmin