Kill phantom jobs automatically? Post: 7112

8 More Discussions You Might Find Interesting

1. AIX

I created a phantom file now i can't delete it?

Ok, somehow i've managed to create two .ksh files with the same name. Impossible i know but somehow i did it by mistake... I was actually copying a file and renaming it as something else but as i was typing the copy name i hit the delete key by mistake and got the ^? characters in the file name...

2. AIX

w shows phantom user

Hi When i use "w" command, It list some users with "-" command. That means these use already logout,but still in the system somewhere, no process but list under the "w" and "who" command.How can i get rid of these user. Can anybody help me out.thanks a lot xiko

3. Shell Programming and Scripting

background jobs exit status and limit the number of jobs to run

i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help. $cat run_job.ksh #!/usr/bin/ksh #################################### typeset -u SCHEMA_NAME=$1 ...

4. Shell Programming and Scripting

waiting on jobs in bash, allowing limited parallel jobs at one time, and then for all to finish

Hello, I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait...

5. Red Hat

Phantom space usage in /

Hi everyone, Got an interesting one (well, interesting to me) I have a box with a 5Gb / mount point. Checking for large files I found nothing and in fact when I did a full du I found that there was only 1.6Gb in use! And yet 100% used in / So there's an unaccounted 3.4Gb somewhere! The...

6. UNIX for Dummies Questions & Answers

Phantom Protocol Configuration File

I've been trying to set up the phantom protocol just to try it out. I compiled it fine, but when I ran it I got an error that the configuration file wouldn't load. I found that file didn't exist, so I created it with a blank file, but got this: ./phantom Loading configuration file...

7. Programming

Phantom Arrays in PL/SQL

Having issue with an oracle stored procedure that fetches 5k array size to an down stream application using oracle client interface. It is creating phantom arrays and keeps sending arrays that do not exist to begin with and congesting the connections. This happened when we upgraded from oracle...

8. Shell Programming and Scripting

Shell script to run multiple jobs and it's dependent jobs

I have multiple jobs and each job dependent on other job. Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE. I need an help how to start. Attaching the JOB dependency...

LEARN ABOUT REDHAT

kill

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)