10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm testing out how to use SIGCHLD and I had a question about intercepting the signal and executing an action in the signal handler.
signal(SIGCHLD,countdown);
What I'm trying to achieve is be able to printf(Hello) every second that child is set to sleep.
I'm setting sleep = 3;
so... (1 Reply)
Discussion started by: l flipboi l
1 Replies
2. Programming
Hi. I have a program whose job it is to manage 15 child processes. Sometimes these children die (sometimes deliberately other times with a SEGV). This causes a SIGCHLD to be sent to my program which uses waitpid() in the signal handler to gather information and, in most cases, restart the child.... (3 Replies)
Discussion started by: jrichemont
3 Replies
3. Solaris
Hi
I would like to display only error messages from my log files while monotring application on my solaris box using tail command.
Is there other way we can monitor please let me know?
In general # tail -f "xyz.log' ---> this will display current activity of the logs, instead i would like... (4 Replies)
Discussion started by: gkrishnag
4 Replies
4. UNIX for Dummies Questions & Answers
I want to know whicj process send the signal SIGCHLD to the parent's child.
Thank you in advance, (1 Reply)
Discussion started by: Puntino
1 Replies
5. UNIX for Dummies Questions & Answers
When the SIGCHLD is sent?
SIGCHLD is sent either a child exits spontaneously (e.g. exit(0)) or it is killed ?
thank you in advance (3 Replies)
Discussion started by: Puntino
3 Replies
6. Programming
Hi,
I have small problem.
In my (concurrent)server programm,
I am handling accept problem from client like this.
sample of server code.
/*******************/
end = 0;
while (! end )
{
sockfd = accept(...)
if(sockfd == -1)
{
if (errno == EINTR) /* this is bcoz... (5 Replies)
Discussion started by: stevenjagan
5 Replies
7. Programming
Hi,
I have 2 processes X and Y. Y is exec() from X. In Y i have an exit handler, which is called when i return from main. With in exit handler i delete and object which in turn calls the destructor of the object, which terminates all the threads of Y.
I believe that SIGCHLD is raised by Y as... (4 Replies)
Discussion started by: supersumanth
4 Replies
8. Programming
Hi,
I have an c++ application which uses the function fork and execvp().
The parent does not wait until the child ends. The parents just creates children and let them do their stuff.
You can see the parent program as a batch-manager.
I have added a SIGCHLD handler to the program:
void... (3 Replies)
Discussion started by: jens
3 Replies
9. UNIX for Advanced & Expert Users
I want to catch SIGCHLD signal in parent process. I can't use wait() system call to catch SIGCHLD according to project requirment.
Operating system linux 3.1
can any one have a solution for this.
Thanking you,
ranjan (2 Replies)
Discussion started by: ranjan
2 Replies
10. Programming
Hello everybody, this is my first post on this forum. I have a program that has a child process that sleeps for 5 second and exit. I'm suppose to modify this program so that when the child exits, the parent reports the exit status of the child, so I also have to deal with SIGINT and SIGQUIT. Can... (1 Reply)
Discussion started by: Unlimited Sky
1 Replies
RFORK(2) BSD System Calls Manual RFORK(2)
NAME
rfork -- manipulate process resources
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
pid_t
rfork(int flags);
DESCRIPTION
Forking, vforking or rforking are the only ways new processes are created. The flags argument to rfork() selects which resources of the
invoking process (parent) are shared by the new process (child) or initialized to their default values. The resources include the open file
descriptor table (which, when shared, permits processes to open and close files for other processes), and open files. The flags argument is
the logical OR of some subset of:
RFPROC If set a new process is created; otherwise changes affect the current process.
RFNOWAIT If set, the child process will be dissociated from the parent. Upon exit the child will not leave a status for the parent to
collect. See wait(2).
RFFDG If set, the invoker's file descriptor table (see intro(2)) is copied; otherwise the two processes share a single table.
RFCFDG If set, the new process starts with a clean file descriptor table. Is mutually exclusive with RFFDG.
RFTHREAD If set, the new process shares file descriptor to process leaders table with its parent. Only applies when neither RFFDG nor
RFCFDG are set.
RFMEM If set, the kernel will force sharing of the entire address space, typically by sharing the hardware page table directly. The
child will thus inherit and share all the segments the parent process owns, whether they are normally shareable or not. The
stack segment is not split (both the parent and child return on the same stack) and thus rfork() with the RFMEM flag may not
generally be called directly from high level languages including C. May be set only with RFPROC. A helper function is provided
to assist with this problem and will cause the new process to run on the provided stack. See rfork_thread(3) for information.
Note that a lot of code will not run correctly in such an environment.
RFSIGSHARE If set, the kernel will force sharing the sigacts structure between the child and the parent.
RFTSIGZMB If set, the kernel will deliver a specified signal to the parent upon the child exit, instead of default SIGCHLD. The signal
number signum is specified by oring the RFTSIGFLAGS(signum) expression into flags. Specifying signal number 0 disables signal
delivery upon the child exit.
RFLINUXTHPN If set, the kernel will deliver SIGUSR1 instead of SIGCHLD upon thread exit for the child. This is intended to mimic certain
Linux clone behaviour.
File descriptors in a shared file descriptor table are kept open until either they are explicitly closed or all processes sharing the table
exit.
If RFPROC is set, the value returned in the parent process is the process id of the child process; the value returned in the child is zero.
Without RFPROC, the return value is zero. Process id's range from 1 to the maximum integer (int) value. The rfork() system call will sleep,
if necessary, until required process resources are available.
The fork() system call can be implemented as a call to rfork(RFFDG | RFPROC) but is not for backwards compatibility.
RETURN VALUES
Upon successful completion, rfork() returns a value of 0 to the child process and returns the process ID of the child process to the parent
process. Otherwise, a value of -1 is returned to the parent process, no child process is created, and the global variable errno is set to
indicate the error.
ERRORS
The rfork() system call will fail and no child process will be created if:
[EAGAIN] The system-imposed limit on the total number of processes under execution would be exceeded. The limit is given by the
sysctl(3) MIB variable KERN_MAXPROC. (The limit is actually ten less than this except for the super user).
[EAGAIN] The user is not the super user, and the system-imposed limit on the total number of processes under execution by a single
user would be exceeded. The limit is given by the sysctl(3) MIB variable KERN_MAXPROCPERUID.
[EAGAIN] The user is not the super user, and the soft resource limit corresponding to the resource argument RLIMIT_NOFILE would be
exceeded (see getrlimit(2)).
[EINVAL] Both the RFFDG and the RFCFDG flags were specified.
[EINVAL] Any flags not listed above were specified.
[EINVAL] An invalid signal number was specified.
[ENOMEM] There is insufficient swap space for the new process.
SEE ALSO
fork(2), intro(2), minherit(2), vfork(2), pthread_create(3), rfork_thread(3)
HISTORY
The rfork() function first appeared in Plan9.
BSD
July 12, 2011 BSD