Sponsored Content
Top Forums UNIX for Dummies Questions & Answers I'm getting killed and I don't know why. Post 302074981 by tphyahoo on Monday 29th of May 2006 06:58:07 AM
Old 05-29-2006
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 08:12 AM..
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

process not getting killed

I have a process that is in the sleeping state "S" and I have tried to stop it with a run control script that I use to stop/start it - but it does not stop. I have tried kill -9 <PID of process> with no change. I imagine that this process is sleeping with the kernel. It does not respond to... (5 Replies)
Discussion started by: finster
5 Replies

2. Solaris

how to start Xsun once it's killed

How can I restart the X window server on my solaris server without rebotting the server? (1 Reply)
Discussion started by: krishan
1 Replies

3. Solaris

Port used needs to be killed

Hi, We are using oracle 10g in a Solaris box. The same box has Informatica also installed. But it runs on port 6001. But whenever the server is restarted the Oracle database picks up the port 6001 and does not allow Informatica to be started. But I am have no clue of which Oracle process is... (2 Replies)
Discussion started by: chrisanto_2000
2 Replies

4. UNIX for Advanced & Expert Users

ls is being killed

Hi There, Hope anyone can give me a hand on AIX oslevel -r 5300-05 Try to "ls *sh" from folder and it return killed, is there any clue on that? 1. perform ls and count ls * | wc -l 0 ksh: 561582 Killed 2. without provide "*" wildcard, the result can be return ls | wc ... (7 Replies)
Discussion started by: darkrainbow
7 Replies

5. UNIX for Advanced & Expert Users

Getting 'Killed' msg

Can anyone explain? I start my unix session on AIX, run tcsh move to a particular directory, let say: cd /test/bin and next i run a command like: grep "test string" /test/bin/* to look for the string in any files in the directory. I am getting a response of Killed. Why is that... (16 Replies)
Discussion started by: gio001
16 Replies

6. Shell Programming and Scripting

Killed by signal 15.

Hi all I have Master script, Main script ,and 4 Child script. Master.sh #!/bin/bash /export/home/user/Main.shMain.sh #!/bin/bash /export/home/user/Child1.sh & /export/home/user/Child2.sh & /export/home/user/Child3.sh & /export/home/user/Child4.sh &I run only Master.sh script... (1 Reply)
Discussion started by: almanto
1 Replies

7. Shell Programming and Scripting

Syncsort is getting killed

Hi All, I am running synsort utility via unix scripts. As soon as the control reaches the syncsort command,Its getting killed. The error message is /proj/cdw/syncsort/dev/copay/CdwWkRvrslFileReformat.syn: 8339696 Killed . Please suggest to overcome this issue. (5 Replies)
Discussion started by: prashantnandi
5 Replies

8. What is on Your Mind?

Has Oracle killed HP-UX

Has Oracle killed HP-UX with their gambit of telling the public they would no longer support Itanium? The company I work for in the Dallas, TX area has had several openings for HP-UX administrators and we're having such a tough time finding qualified people to fill them. I have been searching job... (3 Replies)
Discussion started by: keelba
3 Replies
console(n)						       Tk Built-In Commands							console(n)

__________________________________________________________________________________________________________________________________________________

NAME
console - Control the console on systems without a real console SYNOPSIS
console subcommand ?arg ...? _________________________________________________________________ DESCRIPTION
The console window is a replacement for a real console to allow input and output on the standard I/O channels on platforms that do not have a real console. It is implemented as a separate interpreter with the Tk toolkit loaded, and control over this interpreter is given through the console command. The behaviour of the console window is defined mainly through the contents of the console.tcl file in the Tk library. Except for TkAqua, this command is not available when Tk is loaded into a tclsh interpreter with "package require Tk", as a conventional terminal is expected to be present in that case. In TkAqua, this command is ony available when stdin is /dev/null (as is the case e.g. when the application embedding Tk is started from the Mac OS X Finder). console eval script Evaluate the script argument as a Tcl script in the console interpreter. The normal interpreter is accessed through the consolein- terp command in the console interpreter. console hide Hide the console window from view. Precisely equivalent to withdrawing the . window in the console interpreter. console show Display the console window. Precisely equivalent to deiconifying the . window in the console interpreter. console title ?string? Query or modify the title of the console window. If string is not specified, queries the title of the console window, and sets the title of the console window to string otherwise. Precisely equivalent to using the wm title command in the console interpreter. ACCESS TO THE MAIN INTERPRETER
The consoleinterp command in the console interpreter allows scripts to be evaluated in the main interpreter. It supports two subcommands: eval and record. consoleinterp eval script Evaluates script as a Tcl script at the global level in the main interpreter. consoleinterp record script Records and evaluates script as a Tcl script at the global level in the main interpreter as if script had been typed in at the con- sole. ADDITIONAL TRAP CALLS
There are several additional commands in the console interpreter that are called in response to activity in the main interpreter. These are documented here for completeness only; they form part of the internal implementation of the console and are likely to change or be mod- ified without warning. Output to the console from the main interpreter via the stdout and stderr channels is handled by invoking the tk::ConsoleOutput command in the console interpreter with two arguments. The first argument is the name of the channel being written to, and the second argument is the string being written to the channel (after encoding and end-of-line translation processing has been performed.) When the . window of the main interpreter is destroyed, the tk::ConsoleExit command in the console interpreter is called (assuming the con- sole interpreter has not already been deleted itself, that is.) DEFAULT BINDINGS
The default script creates a console window (implemented using a text widget) that has the following behaviour: [1] Pressing the tab key inserts a TAB character (as defined by the Tcl escape.) [2] Pressing the return key causes the current line (if complete by the rules of info complete) to be passed to the main interpreter for evaluation. [3] Pressing the delete key deletes the selected text (if any text is selected) or the character to the right of the cursor (if not at the end of the line.) [4] Pressing the backspace key deletes the selected text (if any text is selected) or the character to the left of the cursor (of not at the start of the line.) [5] Pressing either Control+A or the home key causes the cursor to go to the start of the line (but after the prompt, if a prompt is present on the line.) [6] Pressing either Control+E or the end key causes the cursor to go to the end of the line. [7] Pressing either Control+P or the up key causes the previous entry in the command history to be selected. [8] Pressing either Control+N or the down key causes the next entry in the command history to be selected. [9] Pressing either Control+B or the left key causes the cursor to move one character backward as long as the cursor is not at the prompt. [10] Pressing either Control+F or the right key causes the cursor to move one character forward. [11] Pressing F9 rebuilds the console window by destroying all its children and reloading the Tcl script that defined the console's be- haviour. Most other behaviour is the same as a conventional text widget except for the way that the <<Cut>> event is handled identically to the <<Copy>> event. EXAMPLE
Not all platforms have the console command, so debugging code often has the following code fragment in it so output produced by puts can be seen while during development: catch {console show} SEE ALSO
destroy(n), fconfigure(n), history(n), interp(n), puts(n), text(n), wm(n) KEYWORDS
console, interpreter, window, interactive, output channels Tk 8.4 console(n)
All times are GMT -4. The time now is 05:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy