when the control reaches function1(), it should get executed in the
background.At the same time main's printf(" ") statement should also get executed.i.e function1() should be independent of the main after it is called.Both should run simultaneously.
Also the background process should not return to main and handle other requests in background (e.g waiting for the msg Q to get filled up).
fork within the program to create a child process and execute the function1 inside the child process
and printf would resume with the parent process
you need to control regarding which should run first parent or child.
Hello all,
Can someone explain to me the advantage between using subshell over a function call in scripts? To me these are the same. Am I wrong to think this? (4 Replies)
Hi all,
I have a script like:
echo Please input list file name:
read listn
for file in `cat $listn.txt`
do
send_file $file
done
normally, I will run the script like:
:. resendfile
Please input list filename:
list1
#Then, the script will resend all file from the list1. However,... (4 Replies)
Hi,
I was trying to run ssh2 command in background... but i got follwoing error message saying that process has been stopped..
+ Stopped(SIGTTOU)
Anyone have any idea about this??? Appreciated your help.. (3 Replies)
Dear all,
I'm writing a KornShell script that calls inside it a function in background mode
#!/bin/ksh
function myfunction
{ . . .}
myfunction |&
. . .
How can I capture the PID of the function myfunction that runs in background?
Thanks in advance
:) (2 Replies)
Looking for a logic where say i have a script called parent_script which is used to call other 4 to 5 child scripts in background as..
cat parent_script # containing 65 lines
1
2
..
35 while read child_script
36 do
37 ./child_script_name&
38 done< ${SCRIPT_LISTS}
39
40 # Need to have... (2 Replies)
Hello everybody,
I'm making a script for running a .bat process on wineconsole, but I want that wineconsole doesn't show up when I call it from the script.
The script is named "reset" and it looks like this:
When I execute it, it will show up the wineconsole window on top, and that is... (3 Replies)
Hii Friends,
I am using Perl CGI. I am running A SCP Command via Perl CGI in Background. Like
system("scp -r machinename:/PathOfFile/ /Path/WhereToCopyIt/ &)
This Copy Process takes some times lets say 15 min.
Now I want When This copy process gets complete then send me... (5 Replies)
Here is some back ground on the script. The script is to poll an arbitrary number of DB's. To do this I am creating a function that takes the file_path to the DB and the min poll interval as arguments. The function will be called for each DB and then ran in the background. The function I was... (6 Replies)
Discussion started by: ryandavison
6 Replies
LEARN ABOUT REDHAT
pthread_atfork
PTHREAD_ATFORK(3) Library Functions Manual PTHREAD_ATFORK(3)NAME
pthread_atfork - register handlers to be called at fork(2) time
SYNOPSIS
#include <pthread.h>
int pthread_atfork(void (*prepare)(void), void (*parent)(void), void (*child)(void));
DESCRIPTION
pthread_atfork registers handler functions to be called just before and just after a new process is created with fork(2). The prepare han-
dler will be called from the parent process, just before the new process is created. The parent handler will be called from the parent
process, just before fork(2) returns. The child handler will be called from the child process, just before fork(2) returns.
One or several of the three handlers prepare, parent and child can be given as NULL, meaning that no handler needs to be called at the cor-
responding point.
pthread_atfork can be called several times to install several sets of handlers. At fork(2) time, the prepare handlers are called in LIFO
order (last added with pthread_atfork, first called before fork), while the parent and child handlers are called in FIFO order (first
added, first called).
To understand the purpose of pthread_atfork, recall that fork(2) duplicates the whole memory space, including mutexes in their current
locking state, but only the calling thread: other threads are not running in the child process. The mutexes are not usable after the fork
and must be initialized with pthread_mutex_init in the child process. This is a limitation of the current implementation and might or
might not be present in future versions.
RETURN VALUE
pthread_atfork returns 0 on success and a non-zero error code on error.
ERRORS
ENOMEM insufficient memory available to register the handlers.
AUTHOR
Xavier Leroy <Xavier.Leroy@inria.fr>
SEE ALSO fork(2), pthread_mutex_lock(3), pthread_mutex_unlock(3).
LinuxThreads PTHREAD_ATFORK(3)