05-26-2016
I'd prefer to fix the code that can't cope with some, say, ill-structured records...
How do the records that cause the code to "hang" differ from the others that make it work well?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I have a C program that takes anywhere from 5 to 100 arguments and I'd like to run it from a script that makes sure it doesnt take too long to execute. If the C program takes more than 5 seconds to execute, i would like the shell script to kill it and return a short message to the user. ... (3 Replies)
Discussion started by: WeezelDs
3 Replies
2. UNIX for Advanced & Expert Users
I have a requirement to check how long a process is running on unix system.If i use ps -ef i am getting the following message
guest 2453638 1998920 0 16:16:05 - 0:00 dsapi_slave 9 8 0
but this is showing only time not the date.Can any one please advice me any script to find out how... (2 Replies)
Discussion started by: ukatru
2 Replies
3. UNIX for Advanced & Expert Users
How do I check if a particular process is running from a certain date and time ? (2 Replies)
Discussion started by: hpuxlxboy
2 Replies
4. UNIX for Dummies Questions & Answers
Here's the scenario
i have this servd process i want to kill, but i want to kill it one time.
bash-2.03# ps -ef | grep servd | grep User123 | wc -l
300
bash-2.03# ps -ef | grep servd | grep User123 | more
User123 2007 2006 0 03:17:09 pts/12 0:00 /usr/bin/su - User123 -c ssh... (2 Replies)
Discussion started by: hrist
2 Replies
5. Shell Programming and Scripting
Gurus,
I am writing a shell script that will be used to automate cold backup of an Oracle Database. The database size is around 300G and will take around 5-6 hours to copy.
I have finished the script till the copy of the datafiles. Now, I am stuck at the point where I need to monitor the... (4 Replies)
Discussion started by: sunpraveen
4 Replies
6. UNIX Desktop Questions & Answers
Hi i am a newbie thanks in advance
i have a process which keeps on running but doesn't use any CPU time and doesn't do the functionality which it is suppose to do .
If i kill the process and start the process again then the process kicks in and starts using CPU time and continues to do its... (3 Replies)
Discussion started by: nick1982
3 Replies
7. UNIX for Dummies Questions & Answers
Consider two servers tst01 and tst02.
i need to log in tst01 and check for the processes which run in tst02.
then based on pid , i need to kill that process.
is it possible to achieve?
I am able to connect to tst02 using ftp.
But the problem is, if i use ps it says invalid command.
... (3 Replies)
Discussion started by: pandeesh
3 Replies
8. UNIX Desktop Questions & Answers
Hi,
I'm new to Linux.
I have a windows server that run many processes on it.
In some cases the processes doesn't exit properly or just stop working and the process needs to be killed.
I was wondering how i can automatically (couple of times a day) check which process doesn't use any CPU... (3 Replies)
Discussion started by: ramikom
3 Replies
9. Shell Programming and Scripting
Hi,
I need a script to kill the process if it running for long time.
Inputs for the scripts:
1.test.sh (will be running fron cron scheduler)
2.1 hr (ie threshold_time - if the test.sh is running for more than 1 hr test.sh has to kill)
Thanks,
Divya (1 Reply)
Discussion started by: Divya Nochiyil
1 Replies
10. Shell Programming and Scripting
I want to run a script that calls remote ssh and if it gets hung, I want to be able to kill that part of the script and run another command in the script
for example I have a statement like this:
if ];
then
export tapes=$(for tape in $(su - nacct -c 'ssh remote1 "cat... (1 Reply)
Discussion started by: newbie2010
1 Replies
LEARN ABOUT REDHAT
killall
KILLALL(1) User Commands KILLALL(1)
NAME
killall - kill processes by name
SYNOPSIS
killall [-e,--exact] [-g,--process-group] [-i,--interactive] [-q,--quiet] [-v,--verbose] [-w,--wait] [-V,--version] [-S,--sid] [-c,--con-
text] [-s,--signal signal] [--] name ...
killall -l
killall -V,--version
DESCRIPTION
killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent.
Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1).
If the command name contains a slash (/), processes executing that particular file will be selected for killing, independent of their name.
killall returns a zero return code if at least one process has been killed for each ilisted command. killall returns zero otherwise.
A killall process never kills itself (but may kill other killall processes).
OPTIONS
-e, --exact
Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be unavailable (i.e.
it is swapped out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries
are skipped. killall prints a message for each skipped entry if -v is specified in addition to -e,
-g, --process-group
Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong-
ing to the same process group were found.
-i, --interactive
Interactively ask for confirmation before killing.
-l, --list
List all known signal names.
-q, --quiet
Do not complain if no processes were killed.
-v, --verbose
Report if the signal was successfully sent.
-V, --version
Display version information.
-w, --wait
Wait for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if
none are left. Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie
state.
-S (Flask only) Specify SID: kill only processes with given SID. Mutually exclusive with -c argument. Must precede other arguments on
command line.
-c (Flask only) Specify security context: kill only processes with given security context. Mutually exclusive with -s. Must precede
other arguments on the command line.
FILES
/proc location of the proc file system
KNOWN BUGS
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.
Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user.
killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.
AUTHORS
Werner Almesberger <Werner.Almesberger@epfl.ch> wrote the original version of psmisc. Since version 20 Craig Small <csmall@small.drop-
bear.id.au> can be blamed.
SEE ALSO
kill(1), fuser(1), pgrep(1), pidof(1), ps(1), kill(2)
Linux March 25, 2001 KILLALL(1)