06-22-2002
thanks.
thanks,i'm trying now
10 More Discussions You Might Find Interesting
1. Programming
unix IPC
i would like to know the method of usage of semaphores on shared memory segments the topic seems very difficult to understand mainly when difrent proceses communicate instantly and how do i avaoid deadlock situation (2 Replies)
Discussion started by: kamathanil
2 Replies
2. Programming
Hello,
I would like to ask you for a little help with program I'm working on. I have problems with signals and synchronizing processes (I'm quite new to this part of programming).
Process "parent" creates new child process "child1" and this process creates new child process "child2". The... (2 Replies)
Discussion started by: Nightwright
2 Replies
3. UNIX for Advanced & Expert Users
Hi all,
How can a process be aware of the signals it handles. I looked at available signal API, but couldn't find any help.
If a process defines it own handler for a signal, the default handler for that signal becomes overridden.
I am interested in getting to know the... (2 Replies)
Discussion started by: bluehive
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am thinking about writing a log daemon for a multi-processed ksh application (yes - I know that high-level language would be a better option).
My question is as follows:
If many processes (many scripts) will try writing to a single log file:
print "message" > common.log
Will it work or... (2 Replies)
Discussion started by: adderek
2 Replies
5. Programming
i am creating children processes using fork system call
every child i create goes to sleep for random time.
when child stops running how can i catch his signal and turminate the child (2 Replies)
Discussion started by: emil2006
2 Replies
6. Programming
i want to write a C chat program that communicates over IPC(inter process communication), that could be run using 2 seperate terminal windows within the same computer. so that wat u type in one terminal window , should appear on the other and vice versa...
could some one please help me with the... (2 Replies)
Discussion started by: localp
2 Replies
7. AIX
Hello,
We are using AIX 5.2 ML 7.
One of the process in its log file said the following and stopped running.
Caught signal=5, exiting.
What would cause the signal 5 to be generated on an AIX box.
Please advise.
Thx
Jerardfjay (2 Replies)
Discussion started by: jerardfjay
2 Replies
8. Programming
Hi all,
Does a background process send a signal to its parent when completed? If so, how might i capture this signal?
I'm trying to write shell in c so that when a background process finishes, it prints a message to the console.
Thanks in advance for any advice. (1 Reply)
Discussion started by: jmelai
1 Replies
9. Emergency UNIX and Linux Support
Hello, everyone.
Here's a program:
pid_t pid = fork();
if (0 == pid) // child process
{
execvp ...;
}
I send a signal (such as SIGINT) to the parent process, the child process receive the signal as well as the parent process.
However I don't want to child process to receive the... (7 Replies)
Discussion started by: jackliang
7 Replies
10. Programming
Hello
I would like to create an application with communication between processes,
application tightly coupled, have you please an idea about an API or
a tool that allows me to generate such application?
Thank you so much (11 Replies)
Discussion started by: chercheur857
11 Replies
pause(2) System Calls Manual pause(2)
NAME
pause - suspend process until signal
SYNOPSIS
DESCRIPTION
suspends the calling process until it receives a signal. The signal must be one that is not currently set to be ignored or blocked
(masked) by the calling process.
If the signal causes termination of the calling process, does not return.
If the signal is by the calling process and control is returned from the signal-catching function (see signal(5)), the calling process
resumes execution from the point of suspension; with a return value of -1 from and set to
APPLICATION USAGE
Threads Considerations
Signal dispositions (such as catch/default/ignore) are shared by all threads in the process and blocked signal masks are maintained by each
thread. Therefore, the signals being waited for should not be ignored by the process or blocked by the calling thread.
will suspend only the calling thread until it receives a signal.
If other threads in the process do not block the signal, the signal may be delivered to another thread in the process and the thread in may
continue waiting. For this reason, the use of is recommended instead of for multi-threaded applications.
For more information regarding signals and threads, refer to signal(5).
SEE ALSO
alarm(2), kill(2), sigwait(2), wait(2), signal(5).
STANDARDS CONFORMANCE
pause(2)