10-05-2006
What do you mean can't be killed? They have pids don't they? Try kill -9 on those pids. If you still can't kill the processes, then that probably means that they are stuck in kernel mode. To kill those processes, you will have to reboot the system.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
Discussion started by: rjohnson
4 Replies
2. UNIX for Dummies Questions & Answers
Hi...
I m working on UNIX z/OS. Actually i have to pass the parameters from the JCL to java-db2 program thru PARM. I am able to pass the arguments but the problem occured is, it is throwing an exception while loading the db2 driver as 'Javaclassnotfound:com.ibm.db2.jcc.DB2Driver'... (0 Replies)
Discussion started by: Sujatha Gowda
0 Replies
3. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
4. Linux
I am using the standard vixie-cron am seeing the following my logs : crond: (username) ORPHAN (no passwd entry) Ordinarily this is a simple matter, there is no corresponding user, but I am using central authentication and the username does exist and is usable via the standard nsswitch mechanism, so... (2 Replies)
Discussion started by: humbletech99
2 Replies
5. UNIX Desktop Questions & Answers
How can we find files that were soft linked to an original file and then the original has been deleted. these soft linked files won't then be accessible. How can we find orphan linked files?
Thanks, (3 Replies)
Discussion started by: Pouchie1
3 Replies
6. Shell Programming and Scripting
Hello I need a script which would mail me the list of processes which are zombie/defunct or orphan.
Please help me in this regard. (7 Replies)
Discussion started by: mehimadri
7 Replies
7. UNIX for Advanced & Expert Users
Our cron job stats its started on Oct20
% ps -ef | grep cron
root 1442044 1 0 Oct 20 - 25:23 /usr/sbin/cron
All the below jobs aixmf,aixgh are triggered from cron only.
user pid ppid date time cmd
gaix 1581282 1 35 16:33:01 - 20:56... (1 Reply)
Discussion started by: karnan
1 Replies
8. Emergency UNIX and Linux Support
The AIX servers that I am working on have been identified as having orphaned user ids & improper gecos for some user ids. Can someone help me with a script to delete the user ids if the orphaned ids are provided in a text file. The home directory set up for the user ids happen to be the... (1 Reply)
Discussion started by: ggayathri
1 Replies
9. UNIX for Beginners Questions & Answers
In solaris, orphan process is put to sleep mode and does not consume any CPU resources. In Linux, orphan process is kept in running state consuming all CPU and Ram resources. Is it the case? Is there a difference on how these operating systems will handle orphan processes?
The route cause of... (10 Replies)
Discussion started by: Belure Pooja B
10 Replies
10. UNIX for Beginners Questions & Answers
I am using DB2 v9 and trying to get country values in comma seperated format using below query
SELECT distinct LISTAGG(COUNTRIES, ',') WITHIN GROUP(ORDER BY EMPLOYEE)
FROM LOCATION ;
Output Achieved
MEXICO,UNITED STATES,INDIA,JAPAN,UNITED KINGDOM,MEXICO,UNITED STATES
The table... (4 Replies)
Discussion started by: Perlbaby
4 Replies
TKILL(1) LAM TOOLS TKILL(1)
NAME
tkill - Terminate LAM on one node.
SYNOPSIS
tkill [-dhvN] [-f killfile]
OPTIONS
-d Turn on debugging mode. This implies -v.
-h Print the command help menu.
-v Be verbose.
-N Pretend; do not take action.
-f killfile Use killfile as the name of the kill file.
DESCRIPTION
The tkill tool terminates the LAM session started by hboot(1) on the local node. tkill makes use of a kill file created by the LAM kernel,
which contains the process identifiers of every LAM process in ASCII format. A SIGHUP (see signal(3)) signal is sent to every process
listed in the kill file. tkill waits a short period of time for each process to die. By adding the debug option, the user can see the
final disposition of each process. The mission is accomplished if all processes end up dead.
In LAM, the first process to be killed is always the kernel. When the kernel receives its termination signal, it propagates the signal to
all of its constituent processes. Therefore, tkill will ordinarily be racing the kernel to kill all other processes. This redundant
aspect of tkill allows it to be used as a general purpose tool in association with hboot(1).
FILES
/tmp/lam-$USER@hostname the kill file, created by the kernel, where $USER is the userid, and hostname is the name of the local
machine
SEE ALSO
hboot(1), lam-helpfile(5)
LAM 7.1.4 July, 2007 TKILL(1)