Sponsored Content
Operating Systems Solaris Privileges : modify dir/file owner by other that's not owner Post 302657429 by sirmark on Sunday 17th of June 2012 04:11:24 PM
Old 06-17-2012
Privileges : modify dir/file owner by other that's not owner

i need to do the following operations in solaris 10:

1.change owner and group owner for files which are not owned by the current user and user group
2.to can delete files in the /tmp directory which are not of the current user
3. allow to a standard user the deletion of files in the /tmp directory which are owned by root


thanks for help!

Last edited by sirmark; 06-17-2012 at 05:18 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to change the owner of the file?

How to change the owner of the file? Can I change the owner of file/ files? I am user and not admin.(not logged as root) (1 Reply)
Discussion started by: redlotus72
1 Replies

2. UNIX for Dummies Questions & Answers

change owner of a file

im running into changing the ownership of a file. I am trying to change the ownership to "system", but it doesn't want to work. I sudo chown system /preferences.plist Password: chown: system: Invalid argument is there a way to read the ownership of a file, something like read chown... (3 Replies)
Discussion started by: CBarraford
3 Replies

3. Solaris

Owner of file gets 'not owner' error for chgrp

Hi Folks, I know that changing users and groups is pretty basic admin, but this one has got me stumped. When I try to change the group of a file for which I am the owner for, it still gives me a 'Not owner' error. For example, when I am logged in as 'webadmin', I have the following file: ... (4 Replies)
Discussion started by: brizrobbo
4 Replies

4. Shell Programming and Scripting

determine owner of a file

Hello, I am on a mission to determine the user of file. I have used the ls -l command but it displays permission, link, user, group, etc, but I just want to display just the name of user of a specified file. Many thanks (4 Replies)
Discussion started by: unibboy
4 Replies

5. UNIX for Advanced & Expert Users

Is there a command to get the owner of a file?

At the moment I'm just using `ls -o` (with `cut`), but `ls` is obviously giving me a lot more output than just the file owner. (9 Replies)
Discussion started by: Bilge
9 Replies

6. UNIX for Dummies Questions & Answers

How to know owner of a file without ls and find command

How to know owner of a file without ls and find command :p (1 Reply)
Discussion started by: swat
1 Replies

7. Shell Programming and Scripting

getting file owner in perl

hi, how can I get the owner of the file ( not uid) on windows plaform. "getpwuid" is not working on windows. I knw it works on unix. Thanks. (2 Replies)
Discussion started by: shellwell
2 Replies

8. UNIX for Advanced & Expert Users

How UNIX admin set up this? how files of 744 of other owner can be removed by another owner?

Hi all, We have some files are under 744 permissions and the the owner is say owner1 and group1. Now we have another user owner2 of group2, owner2 can remove files of the owner1 and the permission of those files are 744, unix admin told us he did some config at his side so we can do that. ... (14 Replies)
Discussion started by: TheGunMan
14 Replies

9. Cybersecurity

Change file owner

What i did: - logged in with acc1 and created a new user acc2 commands used: useradd and passwd. - Then i logged in acc2. but all the files are owned by acc1. Issue: I try to change the owner of the files using chown command . But it gives me a error message. All i want to do is... (13 Replies)
Discussion started by: TotallyConfused
13 Replies

10. UNIX for Dummies Questions & Answers

chown: <file>: Not owner on Solaris 9

Hi, on a Solaris 5.9 machine no user except for root is able to use chown. for exmaple: > touch iamgal > ls -la iamgal -rw-r--r-- 1 galtest1 other 0 Dec 19 08:40 iamgal > chown galu iamgal chown: iamgal: Not owner I have checked about /etc/system and rstchown - it is... (5 Replies)
Discussion started by: galuzan
5 Replies
RMUSER(8)						    BSD System Manager's Manual 						 RMUSER(8)

NAME
rmuser -- remove users from the system SYNOPSIS
rmuser [-yv] [-f file] [username ...] DESCRIPTION
The rmuser utility removes one or more users submitted on the command line or from a file. In removing a user from the system, this utility: 1. Removes the user's crontab(1) entry (if any). 2. Removes any at(1) jobs belonging to the user. 3. Sends a SIGKILL signal to all processes owned by the user. 4. Removes the user from the system's local password file. 5. Removes the user's home directory (if it is owned by the user), including handling of symbolic links in the path to the actual home directory. 6. Removes the incoming mail and POP daemon mail files belonging to the user from /var/mail. 7. Removes all files owned by the user from /tmp, /var/tmp, and /var/tmp/vi.recover. 8. Removes the username from all groups to which it belongs in /etc/group. (If a group becomes empty and the group name is the same as the username, the group is removed; this complements adduser(8)'s per-user unique groups.) 9. Removes all message queues, shared memory segments and semaphores owned by the user. The rmuser utility refuses to remove users whose UID is 0 (typically root), since certain actions (namely, killing all the user's processes, and perhaps removing the user's home directory) would cause damage to a running system. If it is necessary to remove a user whose UID is 0, see vipw(8) for information on directly editing the password file. If rmuser was not invoked with the -y option, it will show the selected user's password file entry and ask for confirmation that the user be removed. It will then ask for confirmation to delete the user's home directory. If the answer is in the affirmative, the home directory and any files and subdirectories under it will be deleted only if they are owned by the user. See pw(8) for more details. As rmuser operates, it informs the user regarding the current activity. If any errors occur, they are posted to standard error and, if it is possible for rmuser to continue, it will. The options are as follows: -f file The rmuser utility will get a list of users to be removed from file, which will contain one user per line. Anything following a hash mark ('#'), including the hash mark itself, is considered a comment and will not be processed. If the file is owned by anyone other than a user with UID 0, or is writable by anyone other than the owner, rmuser will refuse to continue. -y Implicitly answer ``yes'' to any and all prompts. Currently, this includes prompts on whether to remove the specified user and whether to remove the home directory. This option requires that either the -f option be used, or one or more user names be given as command line arguments. -v Enable verbose mode. Normally, the output includes one line per removed user; however, with this option rmuser will be much more chatty about the steps taken. username Identifies one or more users to be removed; if not present, rmuser interactively asks for one or more users to be removed. FILES
/etc/master.passwd /etc/passwd /etc/group /etc/spwd.db /etc/pwd.db SEE ALSO
at(1), chpass(1), crontab(1), finger(1), passwd(1), group(5), passwd(5), adduser(8), pw(8), pwd_mkdb(8), vipw(8) HISTORY
The rmuser utility appeared in FreeBSD 2.2. BUGS
The rmuser utility does not comprehensively search the file system for all files owned by the removed user and remove them; to do so on a system of any size is prohibitively slow and I/O intensive. It is also unable to remove symbolic links that were created by the user in /tmp or /var/tmp, as symbolic links on 4.4BSD file systems do not contain information as to who created them. Also, there may be other files cre- ated in /var/mail other than /var/mail/username and /var/mail/.pop.username that are not owned by the removed user but should be removed. The rmuser utility has no knowledge of YP/NIS, and it operates only on the local password file. BSD
May 10, 2002 BSD
All times are GMT -4. The time now is 10:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy