SIGCHLD trace problem


 
Thread Tools Search this Thread
Top Forums Programming SIGCHLD trace problem
# 8  
Old 09-23-2008
Quote:
Do you have random processes killing the ntpd daemon?
Just in case that ntpd exits for some unexpected reason or error operations.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

using SIGCHLD

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

SIGCHLD interrupts its own handler

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

Log Trace

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

Who sent the process SIGCHLD ?

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

About SIGCHLD

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

adv reqd on SIGCHLD on accept call

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

When is SIGCHLD is raised.

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

signal handler for SIGCHLD

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

catch SIGCHLD signal in parent process

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

Need help with SIGCHLD

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
Login or Register to Ask a Question
GROFF_TRACE(7)                                           Miscellaneous Information Manual                                           GROFF_TRACE(7)

NAME
groff_trace - groff macro package trace.tmac SYNOPSIS
groff -m trace [options ...] [files ...] DESCRIPTION
The trace macro package of groff(1) can be a valuable tool for debugging documents written in the roff formatting language. A call stack trace is protocolled on standard error, this is, a diagnostic message is emitted on entering and exiting of a macro call. This greatly eases to track down an error in some macro. This tracing process is activated by specifying the groff or troff command line option -m trace. This works also with the groffer(1) viewer program. A finer control can be obtained by including the macro file within the document by the groff macro call .mso trace.tmac. Only macros that are defined after this line are traced. If command line option -r trace-full=1 is given (or if this register is set in the document), number and string register assignments together with some other requests are traced also. If some other macro package should be traced as well it must be specified after -m trace on the command line. The macro file trace.tmac is unusual because it does not contain any macros to be called by a user. Instead, the existing macro definition and appending facilities are modified such that they display diagnostic messages. EXAMPLES
In the following examples, a roff fragment is fed into groff via standard input. As we are only interested in the diagnostic messages (standard error) on the terminal, the normal formatted output (standard output) is redirected to the nirvana device /dev/null. The result- ing diagnostic messages are displayed directly below the corresponding example. Command line option Example: sh# echo '. > .de test_macro > .. > .test_macro > .test_macro some dummy arguments > ' | groff -m trace >/dev/null *** .de test_macro *** de trace enter: .test_macro *** trace exit: .test_macro *** de trace enter: .test_macro "some" "dummy" "arguments" *** trace exit: .test_macro "some" "dummy" "arguments" The entry and the exit of each macro call is displayed on the terminal (standard output) -- together with the arguments (if any). Nested macro calls Example: sh# echo '. > .de child > .. > .de parent > .child > .. > .parent > ' | groff -m trace >/dev/null *** .de child *** .de parent *** de trace enter: .parent *** de trace enter: .child *** trace exit: .child *** trace exit: .parent This shows that macro calls can be nested. This powerful feature can help to tack down quite complex call stacks. Activating with .mso Example: sh# echo '. > .de before > .. > .mso trace.tmac > .de after > .. > .before > .after > .before > ' | groff >/dev/null *** de trace enter: .after *** trace exit: .after Here, the tracing is activated within the document, not by a command line option. As tracing was not active when macro before was defined, no call of this macro is protocolled; on the other hand, the macro after is fully protocolled. PROBLEMS
Because trace.tmac wraps the .de request (and its cousins), macro arguments are expanded one level more. This causes problems if an argu- ment contains four backslashes or more to prevent too early expansion of the backslash. For example, this macro call .foo \\n[bar] normally passes `\n[bar]' to macro `.foo', but with the redefined .de request it passes ` [bar]' instead. The solution to this problem is to use groff's E escape which is an escape character not interpreted in copy mode, for example .foo En[bar] FILES
The trace macros are kept in the file trace.tmac located in the tmac directory; see groff_tmac(5) for details. ENVIRONMENT
$GROFF_TMAC_PATH A colon-separated list of additional tmac directories in which to search for macro files; see groff_tmac(5) for details. AUTHOR
Copyright (C) 2002, 2006, 2007, 2008 Free Software Foundation, Inc. This document is distributed under the terms of the FDL (GNU Free Documentation License) version 1.1 or later. You should have received a copy of the FDL on your system, it is also available on-line at the GNU copyleft site <http://www.gnu.org/copyleft/fdl.html>. This document is part of groff, the GNU roff distribution. It was written by Bernd Warken. SEE ALSO
groff(1) An overview of the groff system. troff(1) For details on option -m. groffer(1) A viewer program for all kinds of roff documents. groff_tmac(5) A general description of groff macro packages. groff(7) A short reference for the groff formatting language. A complete reference for all parts of the groff system is found in the groff info(1) file. Groff Version 1.21 25 June 2012 GROFF_TRACE(7)