It is not possible to launch many programs SIMULTANEOUSLY from a single Terminal!
However with VERY small increments in time one can launch as many copies of similar or differing scripts and hope that the OS multi(tasking/threading) takes care of the rest.
Starter example:-
This will launch "somescript.sh" in a separate terminal window and "some_other_script.sh" in another terminal window whilst carrying on with its own work!
There is a caveat to this method but I suspect you'll never come across it...
Last edited by wisecracker; 07-19-2013 at 10:21 AM..
Reason: Typos
Hi All,
I am working on solaris 8 sparc machine with 2 cpu.
I am trying to run my application which generates files. I run multiple instance of the application, but the results don't seem to show as if it were runing parallely.
When i run the application once it takes 12 secs to generate a... (1 Reply)
Hi
I want to run two shell script files parallely. These two scripts are interacting with the database. can any body help on this Pls
Regards
Audippa naidu.M (3 Replies)
Hi
I am looking for some kind of feature in unix that will help me write a script that can invoke multiple processes in parallel. And make sure that the multiple parallel processes complete successfully before I proceed to the next step.
Someone suggested something called timespid or... (6 Replies)
hi i am preparing a set of batches for a set of files sequentially
There is a folder /xyz where all the files reside
now all the files starting with
01 - will be appended for one below other to form a batch batch01
then all the files starting with
02 - will be appended for one below other to... (7 Replies)
Hello everybody,
I have a little problem with one of my program. I made a plugin for collectd (a stats collector for my servers) but I have a problem to make it run in parallel.
My program gathers stats from logs, so it needs to run in background waiting for any new lines added in the log... (0 Replies)
HI All,
I have scenerio where I need to call sub modules through for loop
for (i=0; i<30 ;i++)
{
..
..
..
subroutine 1;
subroutine 2;
}
I want this to be run in parallel
process1
{
...
...
subroutine 1;
subroutine 2; (0 Replies)
Hi
Say I am interested in processing a big data set over shell, and each process individually takes a long time, but many such processes can be pipe-lined, is there a way to do this automatically or efficiently in shell?
For example consider pinging a list addresses upto 5 times each. Of... (5 Replies)
Need urgent help on thread: the goal here is the separtemask will take each image and separate different contours and for each contour in the image it will call handleobject thread. So every for loop will call the handeobject thread. However, object index variable needs to be passed in each... (0 Replies)
Hi,
I am taking up the cue from where I was left in my earlier post ( link given below )
https://www.unix.com/shell-programming-scripting/231107-implement-parallel-processing.html
I actually wanted to know the significance of using the Unix "wait" , which returns
the control from background to... (3 Replies)
I have 10,000 + files, each of which I need to zip using bzip2.
Is ti possible to use bash to create 8 parallel streams sending a new file to be processed from the list when one of the others has finished? (1 Reply)
Discussion started by: garethsays
1 Replies
LEARN ABOUT REDHAT
exit
EXIT(3) Linux Programmer's Manual EXIT(3)NAME
exit - cause normal program termination
SYNOPSIS
#include <stdlib.h>
void exit(int status);
DESCRIPTION
The exit() function causes normal program termination and the the value of status & 0377 is returned to the parent (see wait(2)). All
functions registered with atexit() and on_exit() are called in the reverse order of their registration, and all open streams are flushed
and closed. Files created by tmpfile() are removed.
The C standard specifies two defines EXIT_SUCCESS and EXIT_FAILURE that may be passed to exit() to indicate successful or unsuccessful ter-
mination, respectively.
RETURN VALUE
The exit() function does not return.
CONFORMING TO
SVID 3, POSIX, BSD 4.3, ISO 9899 (``ANSI C'')
NOTES
During the exit processing, it is possible to register additional functions with atexit() and on_exit(). Always the last-registered func-
tion is removed from the chain of registered functions, and invoked. It is undefined what happens if during this processing either exit()
or longjmp() is called.
The use of EXIT_SUCCESS and EXIT_FAILURE is slightly more portable (to non-Unix environments) than that of 0 and some nonzero value like 1
or -1. In particular, VMS uses a different convention.
BSD has attempted to standardize exit codes - see the file <sysexits.h>.
After exit(), the exit status must be transmitted to the parent process. There are three cases. If the parent has set SA_NOCLDWAIT, or has
set the SIGCHLD handler to SIG_IGN, the status is discarded. If the parent was waiting on the child it is notified of the exit status. In
both cases the exiting process dies immediately. If the parent has not indicated that it is not interested in the exit status, but is not
waiting, the exiting process turns into a "zombie" process (which is nothing but a container for the single byte representing the exit sta-
tus) so that the parent can learn the exit status when it later calls one of the wait() functions.
If the implementation supports the SIGCHLD signal, this signal is sent to the parent. If the parent has set SA_NOCLDWAIT, it is undefined
whether a SIGCHLD signal is sent.
If the process is a session leader and its controlling terminal the controlling terminal of the session, then each process in the fore-
ground process group of this controlling terminal is sent a SIGHUP signal, and the terminal is disassociated from this session, allowing it
to be acquired by a new controlling process.
If the exit of the process causes a process group to become orphaned, and if any member of the newly-orphaned process group is stopped,
then a SIGHUP signal followed by a SIGCONT signal will be sent to each process in this process group.
SEE ALSO _exit(2), wait(2), atexit(3), on_exit(3), tmpfile(3)
2001-11-17 EXIT(3)