03-09-2005
processes
write a program create two processes to run a for loop which adds numbers 1 to n , say one process adds odd numbers and other adds even numbers
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is it possible to have a main script (i will call it main.ksh) that executes say, 4 other scripts (sub_prog_1.ksh, sub_prog_2.ksh etc..) from within this main.ksh (simultaneously/in parallel), have them run in the background and communicate back to main.ksh when complete?
My guess is to use... (1 Reply)
Discussion started by: google
1 Replies
2. UNIX for Dummies Questions & Answers
What command string will locate ONLY the PID of a process and ouput only the number of PID of the process? (1 Reply)
Discussion started by: mma_buc_98
1 Replies
3. Shell Programming and Scripting
I want to know how to work the Co-Processes in kornshell scripts. So, I very need some script about Co-Processes!
thanks ...:) (3 Replies)
Discussion started by: javalee
3 Replies
4. UNIX for Dummies Questions & Answers
Can someone tell how to find out how long a process has been running? I want to find something that is usually there that the paging system can check on.
Thanks (4 Replies)
Discussion started by: Beetlejuice
4 Replies
5. Shell Programming and Scripting
I have a file like this.
No. State Query Times User Processed Syslog
1 ready idle 973s 0 /Application/ugsvols/bldata01/logs/imanscript1562.syslog
2 ready idle 803s 83997 13 /Application/ugsvols/bldata01/logs/imanscript1542.syslog
3 ready idle 2954s 106641... (17 Replies)
Discussion started by: Krrishv
17 Replies
6. 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
7. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I needed a little help. It's OS thing.
Suppose I have 2 machine connect over a network, I will call my machines as M1and M2.
If I copy a files from M1 to M2. What tasks are these two machine performing for copy to work.
My assumption is that M1 is performing read action and... (1 Reply)
Discussion started by: vishwesh
1 Replies
9. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
10. UNIX for Dummies Questions & Answers
may i know a command to find processes not attached to a terminal?? (1 Reply)
Discussion started by: riya9
1 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)