![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Who is the parent of a killed process ? | Puntino | UNIX for Dummies Questions & Answers | 6 | 05-13-2008 01:50 AM |
| ls is being killed | darkrainbow | UNIX for Advanced & Expert Users | 7 | 02-20-2008 05:53 PM |
| Port used needs to be killed | chrisanto_2000 | SUN Solaris | 2 | 07-04-2007 04:39 PM |
| process not getting killed | finster | UNIX for Dummies Questions & Answers | 5 | 03-26-2005 09:26 AM |
| Application getting killed after one day ??? Help !!!! | ajphaj | UNIX for Dummies Questions & Answers | 6 | 02-24-2005 08:16 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
|||
|
I'm getting killed and I don't know why.
UPDATE: I think I may have a culprit. I had KDE console history to unlimited, and since there's a lot of output... I'm thinking that may be it. I'd still like to hear advice on how to figure out why processes get killed, if anyone has any! though
****************** There's this script I run that takes several hours to complete. Sometimes it completes successfully, but lately it more often gets killed. It's frustrating, because I need the output from this script to verify that a modification to a program doesn't break anything, and this getting-killed problem is resulting in my testing taking much longer than it otherwise would. I am running the script with time, to keep track of how long it takes, and tee to capture the output, ie: time ./CreateTopTen.pl | tee output-cratetopten.txt When running this, I am sshing into a computer using the SUSE KDE console terminal. What's happening is, the console window is just disappearing on my local computer. When I look at the output created by tee, it just trails off somewhere in the middle. The output file is very large: upwards of 100 megabyes, in case that is relevant. Newbie me doesn't know if my kde console is getting killed from something happening on my local computer, or if it is somehow being killed because of something happening on the remote computer. My main goal is to have the script complete reliably, but for now I just want to more effectively diagnose what is going on. Are killed processes logged anywhere? Is there any way that I can make my script react by logging something when it is killed externally? I am much obliged for any advice! Last edited by tphyahoo; 05-29-2006 at 04:12 AM. |
| Forum Sponsor | ||
|
|
|
|||
|
if you cannot trace the output (by scrolling) with tee command then log the output into a seperate file without tee ( no problem even if the old command is used as such.. ), browse through that log file seperately..
have u registered handlers for viable signals which kernel could deliever to terminate your program? register them, and leave a message upon clean exit that the program has been terminated by such signal. you would be able to step-down at the problem., |
|||
| Google The UNIX and Linux Forums |