03-08-2008
Assuming you can't spawn these off to separate shells where you would:
thatprog &
$progid=$!
sleep $sleeptime
kill $progid
But if you need to be doing other stuff in between, generally you'd capture the PID's of the processes when they start, then watch for those processes still running ("ps -p $pid" if you are using shell), killing them when your conditions dictate.
You might also be able to use "ulimit -t" to set maximum cpu time used if that makes sense.
--
Tony Lawrence
Unix, Linux, Mac OS X Help, Tutorials and support pages
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi guys
I installed this new server with 5.0.7 openserver and i'm getting a lot of this process, if a stop and restart the printer spooler they go away but after a few minutes they appear again.This is how it looks like.
root 372 615 0 - - 00:00:00 <defunct>
root ... (0 Replies)
Discussion started by: josramon
0 Replies
2. Shell Programming and Scripting
hi all,
i would like to write the shell script to monitoring the processing, but if i passing the parameter the number of process is incorrect
how to slove it? many thx
got the correct number of process as following script:
===========================================================... (3 Replies)
Discussion started by: eric_wong_ch
3 Replies
3. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
4. Shell Programming and Scripting
Is there a way I can run a command that will run in the kernel or in the memory and automatically kill certain scripts if they get to <defunct> processes, without having to be monitoring the server manually?
I have a Perl script which runs for 20k members and normally does not have any problems,... (2 Replies)
Discussion started by: ukndoit
2 Replies
5. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
6. Emergency UNIX and Linux Support
Hi all
I have networker running on a RHEL 5.7 and over time it hangs. So the solution backup team proposed is to check if the process is hung, to stop and start it.
Unfortunately for me, the rc script only allows three commands, start, stop and status (no restart option) so I managed to set... (15 Replies)
Discussion started by: hedkandi
15 Replies
7. Red Hat
when system is hung state due to swap, we will reboot it through ILO.
i want to know which process caused system hung. (1 Reply)
Discussion started by: Naveen.6025
1 Replies
8. UNIX for Dummies Questions & Answers
I have a multithreaded usermode program(actually a daemon) which is in hanged state.
To debug it I tried attaching the process to gdb, but the gdb hangs.
gstack also gets hanged.
I peeped into the proc file system and saw the process to be in sleeping state.
/proc/sysrq-trigger I guess... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
9. Shell Programming and Scripting
I wish to monitor if my Tomcat process if Running, Hung, or Shutdown.
I cannot use any third party monitoring tools so i decided to use one of these to test if the tomcat server is responding or not .
1. nslookup
2. telnet
3. ps
The reason I do not use wget / curl is because it will... (2 Replies)
Discussion started by: mohtashims
2 Replies
10. Shell Programming and Scripting
I am writing a script to kick off a process to gather logs on multiple nodes in parallel using "&". These processes create individual log files. Which I would like to filter and convert in CSV format after they are complete. I am facing following issues:
1. Monitor all Processes parallelly.... (5 Replies)
Discussion started by: shunya
5 Replies
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 operands.
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.
EXIT STATUS
The kill utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
Terminate the processes with PIDs 142 and 157:
kill 142 157
Send the hangup signal (SIGHUP) to the process with PID 507:
kill -s HUP 507
Terminate the process group with PGID 117:
kill -- -117
SEE ALSO
builtin(1), csh(1), killall(1), ps(1), sh(1), kill(2), sigaction(2)
STANDARDS
The kill utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 3 AT&T UNIX.
BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided.
BSD
April 28, 1995 BSD