05-18-2006
This is a dangerous script and not really recommended. Make sure you know what you are doing.
I will stick my head out, but claim not responsibility for any damage cause.
The following script is not what you want, but will demonstrate the idea. Do NOT run it as is.
ps -ef |grep "$1" | egrep -v "root|daemon|oracle" > tmpfile
A=`cut -c10-14 tmpfile`
for i in $A
do
echo $i
# kill -9 $i
done
It accepts one parameter (could be the user name etc....) and controlled by the grep "$1" command (if you remove it all processes will be considered).
the egrep is just to ensure we do not kill anything important, in our case root, daemon and oracle processes. You should examine your system and see what else needs to be filtered.
Test your script completely before removing # on the kill. Better be safe than sorry.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am doing some system tuning and figuring out how to write a script that will kill multiple processes or all processes with the same owner. Can someone help me out? Thanks (5 Replies)
Discussion started by: nmajin
5 Replies
2. SuSE
Sir,
I using the following commands in a file (part of a bigger script):
#!/bin/bash
cd /opt/oracle/bin
ls -lt | tail -1 | awk '{print $6}' >> /tmp/ramb.out
If I run this from the command prompt the result is:
2007-05-16
if I run it as a cron job then... (5 Replies)
Discussion started by: rajranibl
5 Replies
3. Shell Programming and Scripting
Hi ,
I have a piece of code ...wherein I need to assign the following ...
1) A command line argument to a variable
e.g origCount=ARGV
2) A unix command to a variable
e.g result=`wc -l testFile.txt`
in my awk shell script
When I do this :
print "origCount" origCount --> I get the... (0 Replies)
Discussion started by: sweta_doshi
0 Replies
4. Shell Programming and Scripting
killall -KILL rdiff-backup
Is it a valid command coz i couldn't find a -KILL option for killall in the man page. (1 Reply)
Discussion started by: proactiveaditya
1 Replies
5. Shell Programming and Scripting
Hi everyone,
when executing this command in unix:
echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error.
here is content of my script:
tdbsrvr$ vi hc.sh
"hc.sh" 22 lines, 509... (4 Replies)
Discussion started by: 4dirk1
4 Replies
6. Shell Programming and Scripting
Hi all,
I've been pulling my hair out with this problem for 3 days:wall: now without success any help would be massively appreciated.
Basically the script is used to shutdown a rails server so a new IP address can be assigned, the shutdown part is taken care of in function_one using the... (2 Replies)
Discussion started by: danmc
2 Replies
7. UNIX for Dummies Questions & Answers
HI Guys,
I hope you are well. I am trying to write a script that gets executed every time i open a shell (cshell). I have two questions about that
1) I need to enter these commands
$ echo $DISPLAY
$ setenv $DISPLAY output_of_echo_$display_command
How can i write a... (2 Replies)
Discussion started by: kaaliakahn
2 Replies
8. Shell Programming and Scripting
I am working with a sh script on a solaris 9 zone (sol 10 host) that grabs information to build the configuration command line. the variables Build64, SSLopt, CONFIGopt, and CC are populated in the script. the script includes
CC=`which gcc`
CONFIGopt=' --prefix=/ --exec-prefix=/usr... (8 Replies)
Discussion started by: oly_r
8 Replies
9. Fedora
:wall:killall -wHi
i need to understand how the -w option works in terms of processes.
If this command is issued does it literally terminate all running processes ..wait for them all to be terminated and then return to standard output ?
Thanks in advance (2 Replies)
Discussion started by: MrRobot
2 Replies
10. UNIX for Beginners Questions & Answers
Hello Forum,
I'm making very good progress on my report thanks to the very helpful people on this forum. I've been able to successfully create my report for my Red Hat servers. But I do have a few ubuntu servers in the mix and I'd like to capture some data from them when an ssh connection is... (8 Replies)
Discussion started by: greavette
8 Replies
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:
-d | -v Be more verbose about what will be done. For a single -d option, a list of the processes that will be sent the signal will
be printed, or a message indicating that no matching processes have been found.
-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.
-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