Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   26626 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

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.	 November 2013	       TRACEHOOK_NOTIFY_JCT(9)

Vote for polarhome