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
KDESU(1)							 KDE User's Manual							  KDESU(1)

NAME
kdesu - Runs a program with elevated privileges SYNOPSIS
kdesu [-c command] [-d] [-f file] [-i icon name] [-n] [-p priority] [-r] [-s] [-t] [-u user] [--noignorebutton] [--attach winid] kdesu [KDE Generic Options] [Qt Generic Options] DESCRIPTION
KDE su is a graphical front end for the UNIX(R)su command for the K Desktop Environment. It allows you to run a program as different user by supplying the password for that user. KDE su is an unprivileged program; it uses the system's su. KDE su has one additional feature: it can optionally remember passwords for you. If you are using this feature, you only need to enter the password once for each command. This program is meant to be started from the command line or from .desktop files. Since kdesu is no longer installed in $(kde4-config --prefix)/bin but in kde4-config --path libexec and therefore not in your Path, you have to use $(kde4-config --path libexec)kdesu to launch kdesu. OPTIONS
-c command This specifies the command to run as root. It has to be passed in one argument. So if, for example, you want to start a new file manager, you would enter at the prompt: $(kde4-config --path libexec)kdesu -c Dolphin -d Show debug information. -f file This option allow efficient use of KDE su in .desktop files. It tells KDE su to examine the file specified by file. If this file is writable by the current user, KDE su will execute the command as the current user. If it is not writable, the command is executed as user user (defaults to root). file is evaluated like this: if file starts with a /, it is taken as an absolute filename. Otherwise, it is taken as the name of a global KDE configuration file. -i icon name Specify icon to use in the password dialog. You may specify just the name, without any extension. -n Do not keep the password. This disables the keep password checkbox in the password dialog. -p priority Set priority value. The priority is an arbitrary number between 0 and 100, where 100 means highest priority, and 0 means lowest. The default is 50. -r Use realtime scheduling. -s Stop the kdesu daemon. This is the daemon that caches successful passwords in the background. This feature may also be disabled with -n when KDE su is initially run. -t Enable terminal output. This disables password keeping. This is largely for debugging purposes; if you want to run a console mode app, use the standard su instead. -u user While the most common use for KDE su is to run a command as the superuser, you can supply any user name and the appropriate password. --noignorebutton Do not display an ignore button. --attach winid Makes the dialog transient for an X app specified by winid. SEE ALSO
su(1) More detailed user documentation is available from help:/kdesu (either enter this URL into Konqueror, or run khelpcenter help:/kdesu). EXAMPLES
Run kfmclient as user jim, and show the Konqueror icon in the password dialog: $(kde4-config --path libexec)kdesu -u jim -i konqueror kfmclient AUTHORS
KDE su was written by Geert Jansen<jansen@kde.org> and Pietro Iglio<iglio@fub.it>. AUTHOR
Lauri Watts <lauri@kde.org> Author. K Desktop Environment 2010-09-18 KDESU(1)
All times are GMT -4. The time now is 02:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy