07-22-2009
On Linux it's pretty simple to do
killall commandname instead of killing things by pid all the time, but it can be a dangerous habit to get into. This command exists on Solaris and, I think, several other flavors, but has a completely different and absolutely literal meaning. It needs no arguments.
---------- Post updated at 03:06 PM ---------- Previous update was at 02:57 PM ----------
Quote:
Originally Posted by
ilikecows
A few years ago I made a chown -R mistake. I found out that the hard way that chown -R user:group .* (the solaris version anyway) will see .. as part of the recursion and change ownership of all files and directories (and everything in them) one level above the directory you are in. I did this in my home directory on the NFS server that shared them out. I ended up owning everyones files...
It's smart enough to reject "." and so not loop forever through the same directory, but nobody thought to reject "..". How odd.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to know if there is a way to send unix commands thru FTP from a mainframe to kick off Autosys Jobs. I just need to send a command from the mainframe to UNIX and have UNIX execute that command. (2 Replies)
Discussion started by: skammer
2 Replies
2. UNIX for Dummies Questions & Answers
hi, can i have a unix like environment where i can do things like chmod, shell scripts and etc.. in redhat instead of the GUI that redhat ofters? (4 Replies)
Discussion started by: yls177
4 Replies
3. News, Links, Events and Announcements
http://www.computerhope.com/unix.htm
http://www.linuxdevcenter.com/linux/cmd/ (0 Replies)
Discussion started by: devotedsinner
0 Replies
4. Shell Programming and Scripting
This is my first time using this forum. My question is simple. I need a book that has the commands code for Linux, if there is such a book, of course.
Thank you (1 Reply)
Discussion started by: ropapi
1 Replies
5. UNIX for Dummies Questions & Answers
I'm working on further developing my Unix skills and I'm just curious what some of the experienced admins out there would consider to be 10 essential commands every admin should know. (12 Replies)
Discussion started by: Arkitech
12 Replies
6. Shell Programming and Scripting
I have many files with info about soft, installed on remote machines.
I need to compare this file with template (soft than must be installed) and output file must content info about software that's not installed.
template.txt
software_name1
software_name2
software_name3.1
... (14 Replies)
Discussion started by: cintlt
14 Replies
7. UNIX for Dummies Questions & Answers
Hi All
I have found that few basic commands in unix have the same syntax in linux as well. I need those commands which differ on Linux platform, with some more advanced options..
For example... awk, sed, tr ... and some more commands with advanced options. I am trying to search on the linux... (1 Reply)
Discussion started by: vee_789
1 Replies
8. UNIX for Beginners Questions & Answers
Hi all,
I'm new to UNIX world and new to this forum. As I observed there are lot of commands that needs to be remembered in UNIX programming. I'm into DevOps and can anyone please tell me what are all the important commands that are useful for DevOps Engineer.
NOTE: Please correct me if my... (3 Replies)
Discussion started by: maxlink
3 Replies
CHOWN(8) BSD System Manager's Manual CHOWN(8)
NAME
chown -- change file owner and group
SYNOPSIS
chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
DESCRIPTION
The chown utility changes the user ID and/or the group ID of the specified files. Symbolic links named by arguments are silently left
unchanged unless -h is used.
The options are as follows:
-f Don't report any failure to change file owner or group, nor modify the exit status to reflect such failures.
-H If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal
are not followed.)
-h If the file is a symbolic link, change the user ID and/or the group ID of the link itself.
-L If the -R option is specified, all symbolic links are followed.
-P If the -R option is specified, no symbolic links are followed. Instead, the user and/or group ID of the link itself are modified.
This is the default. Use -h to change the user ID and/or the group of symbolic links.
-R Change the user ID and/or the group ID for the file hierarchies rooted in the files instead of just the files themselves.
-v Cause chown to be verbose, showing files as the owner is modified.
The -H, -L and -P options are ignored unless the -R option is specified. In addition, these options override each other and the command's
actions are determined by the last one specified.
The owner and group operands are both optional; however, at least one must be specified. If the group operand is specified, it must be pre-
ceded by a colon (``:'') character.
The owner may be either a numeric user ID or a user name. If a user name is also a numeric user ID, the operand is used as a user name. The
group may be either a numeric group ID or a group name. If a group name is also a numeric group ID, the operand is used as a group name.
For obvious security reasons, the ownership of a file may only be altered by a super-user. Similarly, only a member of a group can change a
file's group ID to that group.
DIAGNOSTICS
The chown utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
Previous versions of the chown utility used the dot (``.'') character to distinguish the group name. This has been changed to be a colon
(``:'') character, so that user and group names may contain the dot character.
On previous versions of this system, symbolic links did not have owners.
The -v option is non-standard and its use in scripts is not recommended.
LEGACY DESCRIPTION
In legacy mode, the -R and -RP options do not change the user ID or the group ID of symbolic links.
SEE ALSO
chgrp(1), find(1), chown(2), fts(3), compat(5), symlink(7)
STANDARDS
The chown utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compliant.
HISTORY
A chown utility appeared in Version 1 AT&T UNIX.
BSD
March 31, 1994 BSD