Lines Matching +full:on +full:- +full:the +full:- +full:go
2 --------------
8 This is part of the extensive 'job control' glossary entry.
10 protection from job control signals to jobs it starts --
19 the problem. I'm not clear what happens in Reno; I have
20 the impression that when the controlling process terminates,
21 references to the controlling terminal are converted to
27 Orphaned process groups bear indirectly on this issue. A
29 that is, it's immune to job control signals from the terminal.
33 'Historically, the implementation-dependent process that
35 waiting on them is called "init" and has a process ID of 1.'
37 It goes on to note that it used to be the case that 'init'
38 was responsible for sending SIGHUP to the foreground process
40 vhangup(). It is now the responsibility of the kernel to
41 do this when the controlling process calls _exit(). The
47 In general it appears that the kernel now automatically
49 Specifics are listed on the _exit() page (p50).
51 On setsid():
52 -----------
55 do this -- seems reasonable. B.4.3.2 p 248 implies that this is the
59 Process group leaders cannot call setsid() -- another reason to
60 fork! Of course setsid() causes the current process to become a
62 the controlling terminal acquires the session leader's process
66 ---------------------
70 utility (such as 'getty') and is considered ... outside the scope
71 of POSIX.1.' It goes on to say that historically the first open()
72 of a tty in a session sets the controlling terminal. P130 has the
75 The glossary p12 describes a 'controlling process' as the first
77 to the terminal from the session is revoked if the controlling
78 process exits (see p50, in the discussion of process termination).
81 ------------
87 if we get a segmentation fault etc., print a message on the console
89 (this at least decreases the amount of paper consumed :-)
100 necessary states and state transitions (gleaned from the man page):
101 1: single user shell (with password checking?); on exit, go to 2
102 2: rc script: on exit 0, go to 3; on exit N (error), go to 1
103 3: read ttys file: on completion, go to 4
104 4: multi-user operation: on SIGTERM, go to 7; on SIGHUP, go to 5;
105 on SIGTSTP, go to 6
106 5: clean up mode (re-read ttys file, killing off controlling processes
107 on lines that are now 'off', starting them on lines newly 'on')
108 on completion, go to 4
111 then go to 1 (warn if not all processes died, i.e. wait blocks)
112 Given the -s flag, we start at state 1; otherwise state 2