12-12-2009
Quote:
Originally Posted by
jp2542a
The fact is that there will always be someone who feels the need to make all they see conform to their subjective and restrictive view of the actual relationships of arbitrary systems. Suggesting that "kill" in the unix world has anything to do with humans is not reasonable and points to a more disturbing underlying belief of some people that technical forums should be used as a vehicle of nebulous conformity. That was the reason for my reference to AOL and divine intervention.
I have been here since the internet consisted of less than 1200 modems. Since AOL, there has been dulling of something truly brilliant. I had hoped this would have been something along the James Burke experience rather than what I see today
Sorry for the mini rant..
I'll be quiet now
Actually, I understood your point. I was merely illustrating it :-)
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Need a lot of help, need to find information on unix and how to use it, Has anybody ues the learnkey videos on unix teaching. (5 Replies)
Discussion started by: winter
5 Replies
2. UNIX for Dummies Questions & Answers
To anyone who asks which Unix is the best... or which one I should use...
Probably the best timeline I have ever seen.
Read this link... http://www.levenez.com/unix/history.html#08 (0 Replies)
Discussion started by: Kelam_Magnus
0 Replies
3. UNIX for Dummies Questions & Answers
am a windows Prof .... i deside to go with the UNIX .... but how can i start ......plz help me ........ (1 Reply)
Discussion started by: ekarak
1 Replies
4. UNIX for Dummies Questions & Answers
Hi
I have recently joined a bank as a tester. Initially I will be working on some test scripts and then I will be testing their data warehouse using SQL and Unix. I do have a very basic knowledge and understanding of both unix and sql. I am not sure how I will be using Unix to test their ... (2 Replies)
Discussion started by: kartikkumar84@g
2 Replies
5. Shell Programming and Scripting
Need to automate the following steps (OS--> AIX )
1. cd /advx/R8.1MR2/TOP/logs ( I navigate to this directory)
2. Monitor the current date ULOG for specific error pattern
=> ls -lrt ULOG.08*
-rw-rw-rw- 1 vssrt vssgrp 24370 Aug 01 23:57 ULOG.080112
-rw-rw-rw- 1 vssrt vssgrp ... (6 Replies)
Discussion started by: krchakr
6 Replies
6. What is on Your Mind?
This is an excellent video comment on modern society and the remix is good too:
https://www.youtube.com/watch?v=5DU1B_XkyIk
5DU1B_XkyIk
Watch the video above and post your comments. (3 Replies)
Discussion started by: Neo
3 Replies
7. What is on Your Mind?
Nice UNIX history article by John Loeffler, February, 05th 2019
UNIX: Building The Most Important OS in the World
The most widely used operating system in the world was a project born out of failure. (0 Replies)
Discussion started by: Neo
0 Replies
8. What is on Your Mind?
UNIX.com Hello World HUD YT Video
https://youtu.be/cs3dbPnzDV4
Check it out!
Subscribe, Like, Share, Comment .
Cyber Dystopia (Ep. 2) - The Myth of the Singularity Coming Soon! (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT MOJAVE
killall
KILLALL(1) BSD General Commands Manual KILLALL(1)
NAME
killall -- kill processes by name
SYNOPSIS
killall [-delmsvz] [-help] [-u user] [-t tty] [-c procname] [-SIGNAL] [procname ...]
DESCRIPTION
The killall utility kills processes selected by name, as opposed to the selection by pid as done by kill(1). By default, it will send a TERM
signal to all processes with a real UID identical to the caller of killall that match the name procname. The super-user is allowed to kill
any process.
The options are as follows:
-v Be more verbose about what will be done.
-e Use the effective user ID instead of the (default) real user ID for matching processes specified with the -u option.
-help Give a help on the command usage and exit.
-l List the names of the available signals and exit, like in kill(1).
-m Match the argument procname as a (case sensitive) regular expression against the names of processes found. CAUTION! This
is dangerous, a single dot will match any process running under the real UID of the caller.
-s Show only what would be done, but do not send any signal.
-d Print detailed information about the processes matched, but do not send any signal.
-SIGNAL Send a different signal instead of the default TERM. The signal may be specified either as a name (with or without a lead-
ing SIG), or numerically.
-u user Limit potentially matching processes to those belonging to the specified user.
-t tty Limit potentially matching processes to those running on the specified tty.
-c procname
When used with the -u or -t flags, limit potentially matching processes to those matching the specified procname.
-z Do not skip zombies. This should not have any effect except to print a few error messages if there are zombie processes
that match the specified pattern.
ALL PROCESSES
Sending a signal to all processes with uid XYZ is already supported by kill(1). So use kill(1) for this job (e.g. $ kill -TERM -1 or as root
$ echo kill -TERM -1 | su -m <user>)
EXIT STATUS
The killall command will respond with a short usage message and exit with a status of 2 in case of a command error. A status of 1 will be
returned if either no matching process has been found or not all processes have been signalled successfully. Otherwise, a status of 0 will
be returned.
DIAGNOSTICS
Diagnostic messages will only be printed if requested by -d options.
SEE ALSO
kill(1), sysctl(3)
HISTORY
The killall command appeared in FreeBSD 2.1. It has been modeled after the killall command as available on other platforms.
AUTHORS
The killall program was originally written in Perl and was contributed by Wolfram Schneider, this manual page has been written by Jorg
Wunsch. The current version of killall was rewritten in C by Peter Wemm using sysctl(3).
BSD
January 26, 2004 BSD