05-04-2004
determine the PID of the proccess you wish to kill, then decide how long until you want to kill the process, ie: sleep 5m && kill <pid>.
how you figure out what pid you want to kill though is up to you. you may have to have some type of script that would check the output of ps for the proccess you want to kill, like grep for the string, if grep returns 1 (or whatever it returns when it finds your search string) then you initiate the sleep command for your given amount of time.
9 More Discussions You Might Find Interesting
1. HP-UX
hi, one of the process of hpux startup is this ISL where it consults the AUTO file. is this AUTO file resident in disk?
thanks (5 Replies)
Discussion started by: yls177
5 Replies
2. UNIX for Dummies Questions & Answers
just like what the subject said
but the ip is different
example
if now my IP is 192.168.0.50 and my name is seed
if i wanna terminate 192.168.0.55 with the same nick of mine, seed
can i do that ?? and what is the command ?? (2 Replies)
Discussion started by: SeeD
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
I was working on a shell script with randomly shows a page of text from a randomly selected topic .As soon as the page is displayed it callers a timer script which keeps on running indefinitely until the timer script is killed by the user.
This is where I have the problem,if I press... (2 Replies)
Discussion started by: mervin2006
2 Replies
4. HP-UX
Hi!
Just want to know if there is one command that I can use to kill processes by its name.
Thanks. (1 Reply)
Discussion started by: love833
1 Replies
5. HP-UX
HPUX version B.11.23 as reported by uname -a
Start with default signal I believe is -15
#kill PID
Process still present.
#kill -9 PID
Process still present, even after repeated attempt and waiting.
PPID becomes 1 which is the init process
started at boot time.
So far only way to... (8 Replies)
Discussion started by: matthewdesimone
8 Replies
6. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
7. Shell Programming and Scripting
Hi all , i know i ask a lot of question but these are really hard to solve and important question. I send two scripts:
expect.sh:
#!/usr/local/bin/expect
spawn ssh root@172.30.64.163
expect "login:"
send "root\n"
expect "password:"
send "root\n^M"
interact
and
son.sh:
... (2 Replies)
Discussion started by: fozay
2 Replies
8. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
9. Shell Programming and Scripting
Hi,
While trying to supress password prompt using ssh. I have added .ssh folder manually and generated public key and added to authorized_keys file in the remote machine. But still it's prompting for passwords with the following message:
Permission denied... (5 Replies)
Discussion started by: 116@434
5 Replies
KILL(1) Linux Programmer's Manual KILL(1)
NAME
kill - terminate a process
SYNOPSIS
kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
kill -l [ signal ]
DESCRIPTION
The command kill sends the specified signal to the specified process or process group. If no signal is specified, the TERM signal is sent.
The TERM signal will kill processes which do not catch this signal. For other processes, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
options, and the possibility to specify pids by command name is a local extension.
OPTIONS
pid... Specify the list of processes that kill should signal. Each pid can be one of five things:
n where n is larger than 0. The process with pid n will be signaled.
0 All processes in the current process group are signaled.
-1 All processes with pid larger than 1 will be signaled.
-n where n is larger than 1. All processes in process group n are signaled. When an argument of the form `-n' is given, and it
is meant to denote a process group, either the signal must be specified first, or the argument must be preceded by a `--'
option, otherwise it will be taken as the signal to send.
commandname
All processes invoked using that name will be signaled.
-s signal
Specify the signal to send. The signal may be given as a signal name or number.
-l Print a list of signal names. These are found in /usr/include/linux/signal.h
-a Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.
-p Specify that kill should only print the process id (pid) of the named processes, and not send any signals.
SEE ALSO
bash(1), tcsh(1), kill(2), sigvec(2), signal(7)
AUTHOR
Taken from BSD 4.4. The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.
Linux Utilities 14 October 1994 KILL(1)