Shell Scripts - Killing a job.... Post: 302519715

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Killing processes in scripts

I have a small problem. It's annoying though. I wrote this shell script: # # This script will accept two arguments. The first is a flag and the # second is a time interval. The only valid flag is '-t' which means # the user will specify the interval in seconds, otherwise the # default is 600...

2. Shell Programming and Scripting

killing unix job after the job process completes

Hi, Thanks in advance. i need to kill a unix background running job after that job process completes. i can kill a job by giving the following unix command kill -9 processid how to kill the job after the current process run gets completed ? Appreciate your valuable help. ...

3. Shell Programming and Scripting

check if job still alive and killing it after a certain walltime

Hi! I'm using a script to start a process that might run forever if some parameters are given wrong (it's part of an optimization). I would now like to have the process killed after a certain walltime in that case. So far I get it done with the following lines ./My_process.e & pid=`ps -ef |...

4. Solaris

killing a unix job after the job process gets completed

5. UNIX for Dummies Questions & Answers

CRON job to execute all scripts in a directory

Hi everyone: I'm trying to make a CRON job that will execute Fridays at 7am. I have the following: * 7 * * 5 I've been studying up on CRON and I know to have this in a file and then "crontab filename.txt" to add it to the CRON job list. The CRON part I believe I understand, but I would...

6. Shell Programming and Scripting

Killing a shell script

Hi, If I have a large shell script running as root, say for example like one that copies a ton of files, how would I kill the shell script and any processes that it created? Thanks

7. Shell Programming and Scripting

Paid job for bash shell scripts

Job ad removed

8. Shell Programming and Scripting

cron job is not working for two scripts

Hi Gurus, I have a test unix server in which currently some unix cronjob are running. I have written two script one is a shell script in which env variable are there (in that i am exporting those variables). I have also written a perl script . when i am running at the shell manually like...

9. UNIX for Advanced & Expert Users

Issue while killing the process using autosys job

Hi, I have one autosys job that will retrieve the proccess id's and will kill those processess as follows, pid=`/usr/ucb/ps -auwwxx | grep MAIN |nawk '{print $2}'` kill -9 pid but after executing this particular job, its status is showing as TE(terminated) and the kill process is...

10. UNIX for Dummies Questions & Answers

Executing python scripts via cron job

Hi, I'm executing a python script via cron job. The way it is set up is, I'm editing a file called local00 22 * * * root su - -c "/opt/setup_dir/bin/run_bkp -p" When this job executes, the command-specific logfile and the syslog (where the logs are supposed to go) show half of the logs(no...

LEARN ABOUT OPENDARWIN

kill

KILL(1) 						    BSD General Commands Manual 						   KILL(1)

NAME

     kill -- terminate or signal a process

SYNOPSIS

     kill [-s signal_name] pid ...
     kill -l [exit_status]
     kill -signal_name pid ...
     kill -signal_number pid ...

DESCRIPTION

     The kill utility sends a signal to the processes specified by the pid operand(s).

     Only the super-user may send signals to other users' processes.

     The options are as follows:

     -s signal_name
	     A symbolic signal name specifying the signal to be sent instead of the default TERM.

     -l [exit_status]
	     If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.

     -signal_name
	     A symbolic signal name specifying the signal to be sent instead of the default TERM.

     -signal_number
	     A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.

     The following pids have special meanings:
     -1      If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.

     Some of the more commonly used signals:
     1	     HUP (hang up)
     2	     INT (interrupt)
     3	     QUIT (quit)
     6	     ABRT (abort)
     9	     KILL (non-catchable, non-ignorable kill)
     14      ALRM (alarm clock)
     15      TERM (software termination signal)

     Some shells may provide a builtin kill command which is similar or identical to this utility.  Consult the builtin(1) manual page.

SEE ALSO

     builtin(1), csh(1), killall(1), ps(1), kill(2), sigaction(2)

STANDARDS

     The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.

HISTORY

     A kill command appeared in Version 6 AT&T UNIX.

BUGS

     A replacement for the command ``kill 0'' for csh(1) users should be provided.

BSD
								  April 28, 1995							       BSD