Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Killing process and children
Top Forums Shell Programming and Scripting Killing process and children Post 302283088 by quirkasaurus on Monday 2nd of February 2009 02:00:49 PM
Old 02-02-2009
Quote:
Originally Posted by mark007
Hi

Thank you but the problem here is, my main calling script that begins the rsh, when it receives the kill command, it actually sits and waits for the rsh to fully complete before it enters the killemall function.

If the rsh command takes one hour, then the kill will take one hour to start the killemall function.

Any ideas on how to get around this? I am sure it is designed like this, ie finish the line of code currently being run before running the code specified in "trap". Unfortunately this is not desirable for me as I need it to quit immediately without finishing the current line aka rsh machineb........

Did you try my second suggestion?

I tried fooling around with this concept:

On the remote machine, the main script is called "clam":

Code:
echo $$ > pid
while : ; do
date
sleep 10
done > date_log

On the remote machine, there's a kill-script called "duck":

Code:
(
echo looking for clam process
ps -deaf | fgrep clam
echo killing it:
kill -2 `cat pid`
kill -3 `cat pid`
kill -9 `cat pid`
echo checking again:
ps -deaf | fgrep clam
echo done
) > duck.log 2>&1

On the main host, there's a script called "fish":

Code:
trap 'echo trapped signal; rsh sun03 duck; exit 1' 2 3
rsh sun03 'clam &' &
echo back from sun03
echo waiting now...
wait

I think this covers everything.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Killing a stubborn process...

I have a stubborn process on my OpenBSD box that just refuses to die. It is taking up about half a meg of memory and refuses to die. It appears to be an errant gzip process that was executed from the console on 06 Jan 2002. Here is a snippet of my attempts to kill the gzip process ... (7 Replies)
Discussion started by: auswipe
7 Replies

2. Shell Programming and Scripting

killing process using a script

can I do ps -ef | grep <process_name> and kill the process is it exists? and send a mail to me that the process was found and killed Thanks much... KS (4 Replies)
Discussion started by: skotapal
4 Replies

3. AIX

killing a process from a script

Hey all. I'm brand new to this forum and am looking for some help. I have a script that verifies that the backup tapes are working correctly. Basically is uses 1 command: restore -xpqvf > rootvglog I use this for each volume group that we have. We run this everyday but the problem is, we... (4 Replies)
Discussion started by: jalge2
4 Replies

4. Shell Programming and Scripting

killing a child process

I am calling another script from my main script and making it run in the background,based upon the value of the input provided by the user I want to kill the child process ,I have written this code timer.ksh & PID=$$ print "\n Do you wish to continue .. (Y/N) : \c " read kill_proc if ]... (4 Replies)
Discussion started by: mervin2006
4 Replies

5. UNIX for Dummies Questions & Answers

killing a process

I can kill running processes on my linux red hat system using ctrl-c but cannot do it from command line of another terminal using kill -2 pid. Although I can kill them from command line using kill -9 pid and other signals. I would like to do it using the kill -2 pid. Thanks for your suggestions (6 Replies)
Discussion started by: bbhayana
6 Replies

6. Shell Programming and Scripting

Killing of a process and send a mail if the process doesnot come up within 2 minutes

Hi Friends, I am new to this forum as well as new to shell scripting. I have a problem here and i need someone to solve this. Let us consider there are two processes(abc & def).There is a script which kills these two processes(i.e killtheprocess abc). Here abc is the argument . There is a... (1 Reply)
Discussion started by: Prince89
1 Replies

7. UNIX for Dummies Questions & Answers

killing the process

Hi, First, I am running a scipt.While the script is running I realize that I dont want the script to be run so I am killing the script externally.Before the process gets terminated or killed it should delete all the temporary files created by the script.How to do this?Can anyone help me? ... (3 Replies)
Discussion started by: arthi
3 Replies

8. Shell Programming and Scripting

Killing process!!!!

Hi friends, i m in big trouble.... i have one script which connects two server ...like below.. script1.sh ------------------------------------- bash test.sh & eval x=$@ export x=`echo $x` #echo $x # ssh user@8.2.5.6 bash /mbbv/location/script.sh $x|sed '/Binary file/d'... (1 Reply)
Discussion started by: Shahul
1 Replies

9. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

10. Shell Programming and Scripting

Killing the process ID's

Hi , I have a list of application process id's. Is there a way to kill all the process listed below using the script, except the once which are starting with " Genesis " adm 1522 ABC_Process.tra adm 1939 Genesis_Process.tra adm 2729 Genesis_Archive.tra adm 3259 xyz_Process.tra (5 Replies)
Discussion started by: murali1687
5 Replies

LEARN ABOUT MINIX

rsh

RSH(1)							      General Commands Manual							    RSH(1)

NAME

       rsh - remote shell

SYNOPSIS

       rsh [-n] [-l username] host [command]
       host [-n] [-l username] [command]

DESCRIPTION

       Rsh  connects to the specified host, and executes the specified command.  Rsh copies its standard input to the remote command, the standard
       output of the remote command to its standard output, and the standard error of the remote command to its standard error.   Interrupt,  quit
       and terminate signals are propagated to the remote command; rsh normally terminates when the remote command does.

       The  remote  username  used is the same as your local username, unless you specify a different remote name with the -l option.  This remote
       name must be equivalent (in the sense of rlogin(1)) to the originating account; no provision is made for specifying a password with a  com-
       mand.

       If you omit command, then instead of executing a single command, you will be logged in on the remote host using rlogin(1).

       Shell  metacharacters  which  are  not  quoted  are interpreted on local machine, while quoted metacharacters are interpreted on the remote
       machine.  Thus the command

	      rsh otherhost cat remotefile >> localfile

       appends the remote file remotefile to the localfile localfile, while

	      rsh otherhost cat remotefile ">>" otherremotefile

       appends remotefile to otherremotefile.

OPTIONS

       -l username
	      Specify the remote user name.

       -n     Connect standard input of the remote command to /dev/null.  Do this if rsh should not inadvertently read from standard input.

SEE ALSO

       rcp(1), rlogin(1), rhosts(5).

BUGS

       You cannot run an interactive command (like rogue(6) or vi(1)); use rlogin(1).

4.2 Berkeley Distribution					  April 29, 1985							    RSH(1)
All times are GMT -4. The time now is 12:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy