02-18-2009
Quote:
Originally Posted by
pludi
Usually kill -l will list all available signals on your system, but it's probably the TRAP signal (
description)
Pludi,
Thx for the response. Looks like there could be a multitude of reasons as to why a kernel could generate this signal to a process based on the link.
Shoot, I was hoping it would be more specific than what has been described. However thank you for send me the explanation.
Regards
Jerardfjay
10 More Discussions You Might Find Interesting
1. Programming
signal in process communication:
I 'm a example in sun_unix that signal in process communication
It's here down but I only have freebsd in my machine.
how can i do the same in freebsd
eg:
#include <stdio.h>
#include <signal.h>
#include <unistd.h>
int
main( void ){
void... (2 Replies)
Discussion started by: a9711
2 Replies
2. 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
3. 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
4. Solaris
Rebuilding a server (T2000) from a flash archive I created on another server. Using a Solaris 10/08 DVD to boot from the was going to point it tot he flash archive and pull it over NFS. I've done this many times with success until now.
It initially boots off the DVD, you input the... (5 Replies)
Discussion started by: Probos
5 Replies
5. 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
6. Solaris
Hi,
I am pretty new to Solaris and am trying to upgrade from the OBP.
I go through the process of booting from the cdrom, entering all necessary information and running the upgrade. The system completes analysis and then fail with the
EXITING (caught signal 11) error
I believe that... (5 Replies)
Discussion started by: Seanliam
5 Replies
7. 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
8. Solaris
I get an error after the initializing screen. I am using a DVD/ROM to boot up the installation on a Dell Inspiron 1520. Segmentation fault - core dumped. I have tried to restart multiple times. Please help (1 Reply)
Discussion started by: Jimasaurus
1 Replies
9. Solaris
I created a new Virtual machine and was trying to install Solaris but keep getting this error.:confused:
EXITING (caught signal 11)
Type "install-solaris to restart"
Can't find anything on Google.
This is the iso image I am using "sol-10-u11-ga-x86-dvd"
Followed all the instructions on... (5 Replies)
Discussion started by: newborndba
5 Replies
10. Shell Programming and Scripting
Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
LEARN ABOUT OPENSOLARIS
pause
pause(2) System Calls pause(2)
NAME
pause - suspend process until signal
SYNOPSIS
#include <unistd.h>
int pause(void);
DESCRIPTION
The pause() function suspends the calling process until it receives a signal. The signal must be one that is not currently set to be
ignored by the calling process.
If the signal causes termination of the calling process, pause() does not return.
If the signal is caught by the calling process and control is returned from the signal-catching function (see signal(3C)), the calling
process resumes execution from the point of suspension.
RETURN VALUES
Since pause() suspends thread execution indefinitely unless interrupted by a signal, there is no successful completion return value. If
interrupted, it returns -1 and sets errno to indicate the error.
ERRORS
The pause() function will fail if:
EINTR A signal is caught by the calling process and control is returned from the signal-catching function.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |Async-Signal-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
alarm(2), kill(2), signal(3C), wait(3C), attributes(5), standards(5)
SunOS 5.11 28 Dec 1996 pause(2)