Sponsored Content
Operating Systems HP-UX Hpux pkill,a little help with script Post 302812013 by MadeInGermany on Friday 24th of May 2013 06:27:19 PM
Old 05-24-2013
Interesting idea!
Here is an improved version that takes optional -signal parameter,
and also does some checks.
Code:
#!/bin/ksh -p
export PATH=/bin:/usr/bin:/usr/sbin:/sbin
set -f
prog=${0##*/}

usage(){
 echo "${1:+${prog}: $1}
usage: $prog [-signal] command ,..." >&2
 exit 1
}

case $1 in
-*)
 case $1 in
 -[A-Z][A-Z]*[A-Z]|-[1-9]|-[1-9][0-9]) signal=$1; shift;;
 *) usage "Bad signal";;
 esac
 ;;
esac
if [ $# -ne 1 ]; then
 usage "Bad number of arguments"
fi
comm=$1

UNIX95=1 ps -C "$comm" -o pid= | xargs -i kill $signal {}

 

10 More Discussions You Might Find Interesting

1. Solaris

Diffirence between Kill and Pkill Command???

Diffirence between Kill and Pkill Command??? (1 Reply)
Discussion started by: udayn
1 Replies

2. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

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

3. UNIX for Dummies Questions & Answers

kill/pkill process by CMD info.

I have a process that I'd like to kill. Doing a "ps -fu myusername" gives me: UID PID PPID C STIME TTY TIME CMD myusername 5443 1 0 10:05 ? 00:00:00 /bin/sh /some/path/crap.sh -s /yet/another/path/parentProcess myusername 5593 5443 0 ... (2 Replies)
Discussion started by: mrwatkin
2 Replies

4. Linux

Script migration help from HPUX

Hi, We are looking for the extensive list of Commands/Syntax that were working in HP-UX and will not work on LINUX. We would find such commands and modify them accordingly. Do we have any reference sites or documents. You help would be greatly appreciated. Thanks in advance (2 Replies)
Discussion started by: vijaipersonal
2 Replies

5. Shell Programming and Scripting

Suppressing the terminated message from pkill & killall commands in a bash script

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

6. HP-UX

pwage-hpux-T for Trusted HPUX servers

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

7. Shell Programming and Scripting

Pkill Argument issue

Hi All, I am writing a shell script to kill user processes on all servers using pkill. But when i am passing user id directly ist works but when password userid as variable its not working & getting the below error. # ssh hpadmin@vmtest15.zin33 'sudo /usr/bin/pkill -u $unixid'... (2 Replies)
Discussion started by: ajaincv
2 Replies

8. UNIX for Advanced & Expert Users

pkill won't work on firefox anymore

Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies

9. UNIX and Linux Applications

Unix pkill error; does wily obstruct me killing the process?

have two scripts on Unix; one that starts some processes and the other one for killing a process. At first, I ran the .sh without WILY in it and it worked perfectly; in this way, I could also ran my stopper process. However I need WILY in this so I added it to my script but this time, a message... (1 Reply)
Discussion started by: nerdogan551
1 Replies

10. HP-UX

Hpux and bacula script

# bacula status /opt/bacula/bin/bacula-ctl-fd: UNIX95=1;: not found bacula-fd is stopped #! /bin/sh # # bacula-ctl-fd This shell script takes care of starting and stopping # the bacula File daemon. # # This is pretty much watered down version of the RedHat script # that... (9 Replies)
Discussion started by: Linusolaradm1
9 Replies
KILL(1) 							   User Commands							   KILL(1)

NAME
kill - terminate a process SYNOPSIS
kill [-s signal|-p] [-q sigval] [-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 processes by command name are a local extension. If sig is 0, then no signal is sent, but error checking is still performed. 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 signal Specify the signal to send. The signal may be given as a signal name or number. -l, --list [signal] Print a list of signal names, or convert signal given as argument to a name. The signals are found in /usr/include/linux/signal.h -L, --table Similar to -l, but will print signal names and their corresponding numbers. -a, --all Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process. -p, --pid Specify that kill should only print the process id (pid) of the named processes, and not send any signals. -q, --queue sigval Use sigqueue(2) rather than kill(2) and the sigval argument is used to specify an integer to be sent with the signal. If the receiving process has installed a handler for this signal using the SA_SIGINFO flag to sigaction(2), then it can obtain this data via the si_value field of the siginfo_t structure. NOTES
It is not possible to send a signal to explicitly selected thread in a multithreaded process by kill(2) syscall. If kill(2) is used to send a signal to a thread group, then kernel selects arbitrary member of the thread group that has not blocked the signal. For more details see clone(2) CLONE_THREAD description. The command kill(1) as well as syscall kill(2) accepts TID (thread ID, see gettid(2)) as argument. In this case the kill behavior is not changed and the signal is also delivered to the thread group rather than to the specified thread. 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>. AVAILABILITY
The kill command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util- linux/>. util-linux March 2013 KILL(1)
All times are GMT -4. The time now is 06:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy