1 diff -Nru sysvinit-2.78/man/halt.8 sysvinit-2.78.new/man/halt.8
2 --- sysvinit-2.78/man/halt.8 Tue Aug 24 11:45:21 1999
3 +++ sysvinit-2.78.new/man/halt.8 Sat Apr 15 20:39:20 2000
7 \fBHalt\fP notes that the system is being brought down in the file
8 -\fI/var/log/wtmp\fP, and then either tells the kernel to halt, reboot or
9 +\fI/var/log/wtmpx\fP, and then either tells the kernel to halt, reboot or
10 poweroff the system. If \fBhalt\fP or \fBreboot\fP is called when the system is
11 \fInot\fP in runlevel \fB0\fP or \fB6\fP,
12 \fBshutdown\fP(8) will be invoked instead (with the flag \fB-h\fP or \fB-r\fP).
15 Don't sync before reboot or halt.
17 -Don't actually reboot or halt but only write the wtmp record
18 -(in the \fI/var/log/wtmp\fP file).
19 +Don't actually reboot or halt but only write the wtmpx record
20 +(in the \fI/var/log/wtmpx\fP file).
22 -Don't write the wtmp record. The \fB\-n\fP flag implies \fB\-d\fP.
23 +Don't write the wtmpx record. The \fB\-n\fP flag implies \fB\-d\fP.
25 Force halt or reboot, don't call \fBshutdown\fP(8).
28 never be called directly. From release 2.74 on \fBhalt\fP and \fBreboot\fP
29 invoke \fBshutdown\fP(8) if the system is not in runlevel 0 or 6. This
30 means that if \fBhalt\fP or \fBreboot\fP cannot find out the current
31 -runlevel (for example, when \fI/var/run/utmp\fP hasn't been initialized
32 +runlevel (for example, when \fI/var/run/utmpx\fP hasn't been initialized
33 correctly) \fBshutdown\fP will be called, which might not be what you want.
34 Use the \fB-f\fP flag if you want to do a hard \fBhalt\fP or \fBreboot\fP.
36 diff -Nru sysvinit-2.78/man/init.8 sysvinit-2.78.new/man/init.8
37 --- sysvinit-2.78/man/init.8 Fri Feb 11 12:15:07 2000
38 +++ sysvinit-2.78.new/man/init.8 Sat Apr 15 20:40:11 2000
42 When starting a new process, \fBinit\fP first checks whether the file
43 -\fI/etc/initscript\fP exists. If it does, it uses this script to
44 +\fI/etc/sysconfig/initscript\fP exists. If it does, it uses this script to
47 Each time a child terminates, \fBinit\fP records the fact and the reason
48 -it died in \fB/var/run/utmp\fP and \fB/var/log/wtmp\fP,
49 +it died in \fB/var/run/utmpx\fP and \fB/var/log/wtmpx\fP,
50 provided that these files exist.
51 .SH CHANGING RUNLEVELS
52 After it has spawned all of the processes specified, \fBinit\fP waits
58 +/etc/sysconfig/initscript
75 diff -Nru sysvinit-2.78/man/initscript.5 sysvinit-2.78.new/man/initscript.5
76 --- sysvinit-2.78/man/initscript.5 Fri Dec 24 23:31:21 1999
77 +++ sysvinit-2.78.new/man/initscript.5 Sat Apr 15 20:38:20 2000
80 initscript \- script that executes inittab commands.
82 -/bin/sh /etc/initscript id runlevels action process
83 +/bin/sh /etc/sysconfig/initscript id runlevels action process
85 -When the shell script \fI/etc/initscript\fP is present, \fBinit\fP
86 +When the shell script \fI/etc/sysconfig/initscript\fP is present, \fBinit\fP
87 will use it to execute the commands from \fIinittab\fP.
88 This script can be used to set things like \fBulimit\fP and
89 \fBumask\fP default values for every process.
91 This is a sample initscript, which might be installed on your
92 -system as \fI/etc/initscript.sample\fP.
93 +system as \fI/etc/sysconfig/initscript.sample\fP.
98 # initscript Executed by init(8) for every program it
99 # wants to spawn like this:
101 -# /bin/sh /etc/initscript <id> <level> <action> <process>
102 +# /bin/sh /etc/sysconfig/initscript <id> <level> <action> <process>
105 # Set umask to safe level, and enable core dumps.
111 +/etc/sysconfig/initscript.
113 Miquel van Smoorenburg ,<miquels@cistron.nl>
115 diff -Nru sysvinit-2.78/man/inittab.5 sysvinit-2.78.new/man/inittab.5
116 --- sysvinit-2.78/man/inittab.5 Tue May 19 10:17:37 1998
117 +++ sysvinit-2.78.new/man/inittab.5 Sat Apr 15 20:40:31 2000
119 specifies the process to be executed. If the process field starts with
122 -will not do utmp and wtmp accounting for that process. This is needed for
123 -gettys that insist on doing their own utmp/wtmp housekeeping. This is also
124 +will not do utmpx and wtmp accounting for that process. This is needed for
125 +gettys that insist on doing their own utmpx/wtmpx housekeeping. This is also
129 diff -Nru sysvinit-2.78/man/last.1 sysvinit-2.78.new/man/last.1
130 --- sysvinit-2.78/man/last.1 Thu Jul 29 12:50:34 1999
131 +++ sysvinit-2.78.new/man/last.1 Sat Apr 15 20:38:20 2000
136 -searches back through the file \fB/var/log/wtmp\fP (or the file
137 +searches back through the file \fB/var/log/wtmpx\fP (or the file
138 designated by the \fB\-f\fP flag) and displays a list of all
139 users logged in (and out) since that file was created. Names of users
140 and tty's can be given, in which case \fBlast\fP will show only those entries
144 \fBLastb\fP is the same as \fBlast\fP, except that by default it shows a log
145 -of the file \fB/var/log/btmp\fP, which contains all the bad login attempts.
146 +of the file \fB/var/log/btmpx\fP, which contains all the bad login attempts.
151 This option is like \fB-d\fP in that it displays the IP number of the remote
152 host, but it displays the IP number in numbers-and-dots notation.
154 -Read an old-type wtmp file (written by linux-libc5 applications).
155 +Read an old-type wtmpx file (written by linux-libc5 applications).
157 Display the system shutdown entries and run level changes.
160 -The files \fIwtmp\fP and \fIbtmp\fP might not be found. The system only
161 +The files \fIwtmpx\fP and \fIbtmpx\fP might not be found. The system only
162 logs information in these files if they are present. This is a local
163 configuration issue. If you want the files to be used, they can be
164 created with a simple \fBtouch\fP(1) command (for example,
165 -\fItouch /var/log/wtmp\fP).
166 +\fItouch /var/log/wtmpx\fP).
177 diff -Nru sysvinit-2.78/man/runlevel.8 sysvinit-2.78.new/man/runlevel.8
178 --- sysvinit-2.78/man/runlevel.8 Tue May 27 12:33:54 1997
179 +++ sysvinit-2.78.new/man/runlevel.8 Sat Apr 15 20:38:20 2000
181 runlevel -- find the current and previous system runlevel.
193 +.IR /var/run/utmpx )
194 to locate the runlevel record, and then
195 prints the previous and current system runlevel on its standard output,
196 separated by a single space. If there is no previous system
197 runlevel, the letter \fBN\fP will be printed instead.
202 file exists, or if no runlevel record can be found,
204 prints the word \fBunknown\fP and exits with an error.
206 is also available in the environment variables \fBRUNLEVEL\fP and
211 -The name of the \fIutmp\fP file to read.
214 +The name of the \fIutmpx\fP file to read.
221 Miquel van Smoorenburg, miquels@cistron.nl
222 diff -Nru sysvinit-2.78/man/shutdown.8 sysvinit-2.78.new/man/shutdown.8
223 --- sysvinit-2.78/man/shutdown.8 Mon Jun 22 12:43:59 1998
224 +++ sysvinit-2.78.new/man/shutdown.8 Sat Apr 15 20:38:20 2000
226 argument (add this to the invocation of shutdown in /etc/inittab),
227 it checks to see if the file \fI/etc/shutdown.allow\fP is present.
228 It then compares the login names in that file with the list of people
229 -that are logged in on a virtual console (from \fI/var/run/utmp\fP). Only
230 +that are logged in on a virtual console (from \fI/var/run/utmpx\fP). Only
231 if one of those authorized users \fBor root\fP is logged in, it will
232 proceed. Otherwise it will write the message