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)NAMEtracehook_notify_jctl - report about job control stop/continueSYNOPSISint tracehook_notify_jctl(int notify, int why);ARGUMENTSnotify zero, CLD_STOPPED or CLD_CONTINUED why CLD_STOPPED or CLD_CONTINUEDDESCRIPTIONThis 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 |
---|
siginfo(3head) - sunos |
siginfo.h(3head) - opensolaris |
enum_utrace_signal_action(9) - suse |
siginfo(5) - osf1 |
siginfo.h(3head) - centos |
Similar Topics in the Unix Linux Community |
---|
Migrating to UNIX |
Update kernel Linux without reboot?! |
SOCKS proxy & PAM configuration exposure |
Tar Command |
Shopt -s histappend |