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
12-25-2003 05:28 PM
12-25-2003 05:28 PM
chown
For ex:
ll test1, the output as below
--------- file1 test1 users
Then, how to let user test1 can't change owner and group, I try chown bin:bin file1, it's ok to change it, but I don't want to change the user file owner and group, only the root can change it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-25-2003 07:20 PM
12-25-2003 07:20 PM
Re: chown
If you want to disable the chown for a user.Make sure that is home directory and files are not owned by him.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-25-2003 07:23 PM
12-25-2003 07:23 PM
Re: chown
let root own the file.
Or follow the advice in the prior post.
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
12-25-2003 07:30 PM
12-25-2003 07:30 PM
Re: chown
Any impact or security issue on this? Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-25-2003 08:59 PM
12-25-2003 08:59 PM
Re: chown
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2003 12:18 AM
12-26-2003 12:18 AM
Re: chown
I think, the user must have rights to write for the direcory and the file. The access for file1 is nothing. Changing the owner ship for a non root user to another user wont work.
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2003 05:41 AM
12-26-2003 05:41 AM
Re: chown
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-28-2003 08:34 PM
12-28-2003 08:34 PM
Re: chown
The right to alter DAC information (permission bits or ACL entries). Change permission is granted to object (file) owners and to privileged users.
so even a "chacl (${ownername}.%, ---) *" should not work. However, i remember i examinded the veritas acl-version (that comes with jfs4 if memory servers me well), and that is had a different behaviour than the standard acl. Unfortunatly, i don't have any system with the veritas acl-soft on, so i can't help you any further.