suse man page for tracehook_notify_jctl

Query: tracehook_notify_jctl

OS: suse

Section: 9

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

TRACEHOOK_NOTIFY_JCT(9) 					 Kernel Internals					   TRACEHOOK_NOTIFY_JCT(9)

NAME
tracehook_notify_jctl - report about job control stop/continue
SYNOPSIS
int tracehook_notify_jctl(int notify, int why);
ARGUMENTS
notify zero, CLD_STOPPED or CLD_CONTINUED why CLD_STOPPED or CLD_CONTINUED
DESCRIPTION
This is called when we might call do_notify_parent_cldstop. notify is zero if we would not ordinarily send a SIGCHLD, or is the CLD_STOPPED or CLD_CONTINUED .si_code for SIGCHLD. why is CLD_STOPPED when about to stop for job control; we are already in TASK_STOPPED state, about to call schedule. It might also be that we have just exited (check PF_EXITING), but need to report that a group-wide stop is complete. why is CLD_CONTINUED when waking up after job control stop and ready to make a delayed notify report. Return the CLD_* value for SIGCHLD, or zero to generate no signal. Called with the siglock held. Kernel Hackers Manual 2.6. July 2010 TRACEHOOK_NOTIFY_JCT(9)
Related Man Pages
ods-control(8) - debian
struct_utrace_engine_ops(9) - suse
siginfo(5) - osf1
siginfo(3head) - opensolaris
siginfo.h(3head) - centos
Similar Topics in the Unix Linux Community
Change directory error
Migrating to UNIX
Tar Command
The Future of the PM (Private Message) System at UNIX.com
32 bit process addressing more than 4GB