10-05-2014
How to kill a script and all its subprocesses?
I'd like to terminate scripts.
These scripts are not by me, but other persons. These contain other programs such as ping, nmap, arp, etc.
If such a script is running, how can I terminate this script AND all processes called by this script?
These scripts are big so terminating all programs (pkill ping, pkill nmap etc.) is not an option.
Is there anything like "pkill script.sh" killing the script and all processes?
I startet a simple script "test.sh" containing nothing but a "ping www.google.com".
Using "ps ax | grep test.sh" returned nothing, so there is no test.sh in the process list. There is a ping process, but as written before, killing this is not an option.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi!!
Is there a possibility to call/start a subproces using ksh ??
Hope that there is somebody to help me.
thanks in advance.
Corine (3 Replies)
Discussion started by: TheBlueLady
3 Replies
2. Shell Programming and Scripting
Hi all!
I wirte a little Shell Script, that kill pids by programm names. For example, when i want to kill any pid of xmms i use this command:
kill -9 `ps -A | awk ' ($4=="xmms") {print $1}'`
To put this in a "killprg" script i use the following linkes:
#!/bin/bash
echo ""
echo "Programm... (2 Replies)
Discussion started by: donald1111
2 Replies
3. Shell Programming and Scripting
Hello guys,
I have a process named monitoreo, with 'monitoreo start' my process start until i kill them, now i want to do 'monitoreo stop' to kill them.
After 'monitoreo start' i have this process running:
ps -af
UID PID PPID C STIME TTY TIME CMD
ati 10958 1495 ... (5 Replies)
Discussion started by: Lestat
5 Replies
4. UNIX for Advanced & Expert Users
Hi All,
I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages.
How can i terminate this daemon ? ? ?
Regards,
Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies
5. UNIX for Dummies Questions & Answers
I'm going through my UNIX book and came across a section on Customization and Subprocesses.
Can someone tell me what a subprocess is -- for example, when the book says "Which shell 'thing' are known to subprocesses" what exactly does it mean? The book just talks about it without defining it... (10 Replies)
Discussion started by: Straitsfan
10 Replies
6. Shell Programming and Scripting
Hello all... new to these forums and a bit of a newbie with linux aswell.
I need to figure out how to write a shell script to kill a process by name as given to the script as an argument. I've got that part working OK, but i need to make sure that the script does not allow processes that are... (6 Replies)
Discussion started by: cannon1707
6 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am using the below command to kill the firefox process i have opened in Redhat 5.
ps -ef|grep fire|grep -v grep|awk '{print $2}'|xargs kill -9
If i execute the above command in terminal it works good and kills session.
but when i use alias for that it is not working.
alias... (2 Replies)
Discussion started by: nokiak810
2 Replies
8. Shell Programming and Scripting
Hi ,I need your help to kill the script itself if run for more than 10 mins .
main.sh
nohup ./a1.sh param1 &
nohup ./a2.sh param1 &
wait
#Wait for 2 scripts to complete and and kill the process if run more than 10 mins
---
Thanks inadvace
MR
Please view this code tag... (2 Replies)
Discussion started by: mohan705
2 Replies
9. Shell Programming and Scripting
Good afternoon
I need to KILL a process in a single command sentence, for example:
kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'`
That sentence Kills the process ID corresponding to the program CAL255.4ge.
However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
10. Shell Programming and Scripting
all,
i've been reading to try and get an abstract idea of the process effeciency of commands , sed, bash, perl, awk, find, grep, etc
which processes will spawn?, fork?, launch subshell?, etc and under what conditions?
how do you know which commands have the faster and better stdio... (2 Replies)
Discussion started by: f77hack
2 Replies
LEARN ABOUT REDHAT
run-parts
RUN-PARTS(8) System Manager's Manual RUN-PARTS(8)
NAME
run-parts - run scripts or programs in a directory
SYNOPSIS
run-parts [--test] [--verbose] [--report] [--lsbsysinit] [--regex=RE] [--umask=umask] [--arg=argument] [--exit-on-error] [--help] [--ver-
sion] [--list] [--reverse] [--] DIRECTORY
run-parts -V
DESCRIPTION
run-parts runs all the executable files named within constraints described below, found in directory directory. Other files and directo-
ries are silently ignored.
If neither the --lsbsysinit option nor the --regex option is given then the names must consist entirely of ASCII upper- and lower-case let-
ters, ASCII digits, ASCII underscores, and ASCII minus-hyphens.
If the --lsbsysinit option is given, then the names must not end in .dpkg-old or .dpkg-dist or .dpkg-new or .dpkg-tmp, and must belong to
one or more of the following namespaces: the LANANA-assigned namespace (^[a-z0-9]+$); the LSB hierarchical and reserved namespaces
(^_?([a-z0-9_.]+-)+[a-z0-9]+$); and the Debian cron script namespace (^[a-zA-Z0-9_-]+$).
If the --regex option is given, the names must match the custom extended regular expression specified as that option's argument.
Files are run in the lexical sort order (according to the C/POSIX locale character collation rules) of their names unless the --reverse
option is given, in which case they are run in the opposite order.
OPTIONS
--test print the names of the scripts which would be run, but don't actually run them.
--list print the names of the all matching files (not limited to executables), but don't actually run them. This option cannot be used with
--test.
-v, --verbose
print the name of each script to stderr before running.
--report
similar to --verbose, but only prints the name of scripts which produce output. The script's name is printed to whichever of stdout
or stderr the script first produces output on.
--reverse
reverse the scripts' execution order.
--exit-on-error
exit as soon as a script returns with a non-zero exit code.
--lsbsysinit
use LSB namespaces instead of classical behavior.
--new-session
run each script in a separate process session. If you use this option, killing run-parts will not kill the currently running
script, it will run until completion.
--regex=RE
validate filenames against custom extended regular expression RE. See the EXAMPLES section for an example.
-u, --umask=umask
sets the umask to umask before running the scripts. umask should be specified in octal. By default the umask is set to 022.
-a, --arg=argument
pass argument to the scripts. Use --arg once for each argument you want passed.
-- specifies that this is the end of the options. Any filename after -- will be not be interpreted as an option even if it starts with
a hyphen.
-h, --help
display usage information and exit.
-V, --version
display version and copyright and exit.
EXAMPLES
Print the names of all files in /etc that start with `p' and end with `d':
run-parts --list --regex '^p.*d$' /etc
COPYRIGHT
Copyright (C) 1994 Ian Jackson.
Copyright (C) 1996 Jeff Noxon.
Copyright (C) 1996, 1997, 1998 Guy Maor
Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Clint Adams
run-parts is free software; see the GNU General Public License version 2 or later for copying conditions. There is no warranty.
Debian 27 Jun 2012 RUN-PARTS(8)