cleanup use of .Nm
This commit is contained in:
parent
92f7af5b8d
commit
7da448585a
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: init.8,v 1.10 1997/07/19 16:58:47 perry Exp $
|
||||
.\" $NetBSD: init.8,v 1.11 1997/09/15 01:56:08 lukem Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1991, 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -43,21 +43,21 @@
|
|||
.Nm init
|
||||
.Nd process control initialization
|
||||
.Sh SYNOPSIS
|
||||
.Nm init
|
||||
.Nm
|
||||
.Sh DESCRIPTION
|
||||
The
|
||||
.Nm init
|
||||
.Nm
|
||||
program
|
||||
is the last stage of the boot process.
|
||||
It normally runs the automatic reboot sequence as described in
|
||||
.Xr reboot 8 ,
|
||||
and if this succeeds, begins multi-user operation.
|
||||
If the reboot scripts fail,
|
||||
.Nm init
|
||||
.Nm
|
||||
commences single user operation by giving
|
||||
the super-user a shell on the console.
|
||||
The
|
||||
.Nm init
|
||||
.Nm
|
||||
program may be passed parameters
|
||||
from the boot program to
|
||||
prevent the system from going multi-user and to instead execute
|
||||
|
@ -67,27 +67,27 @@ later be made to go to multi-user by exiting the
|
|||
single-user shell (with ^D).
|
||||
This
|
||||
causes
|
||||
.Nm init
|
||||
.Nm
|
||||
to run the
|
||||
.Pa /etc/rc
|
||||
start up command file in fastboot mode (skipping disk checks).
|
||||
.Pp
|
||||
If the
|
||||
.Nm console
|
||||
.Sq console
|
||||
entry in the
|
||||
.Xr ttys 5
|
||||
file is marked ``insecure'',
|
||||
then
|
||||
.Nm init
|
||||
.Nm
|
||||
will require that the superuser password be
|
||||
entered before the system will start a single-user shell.
|
||||
The password check is skipped if the
|
||||
.Nm console
|
||||
.Sq console
|
||||
is marked as ``secure''.
|
||||
.Pp
|
||||
The kernel runs with four different levels of security.
|
||||
Any superuser process can raise the security level, but only
|
||||
.Nm init
|
||||
.Nm
|
||||
can lower it.
|
||||
Security levels are defined as follows:
|
||||
.Bl -tag -width flag
|
||||
|
@ -134,11 +134,11 @@ and
|
|||
for details.
|
||||
.Pp
|
||||
In multi-user operation,
|
||||
.Nm init
|
||||
.Nm
|
||||
maintains
|
||||
processes for the terminal ports found in the file
|
||||
.Xr ttys 5 .
|
||||
.Nm Init
|
||||
.Nm
|
||||
reads this file, and executes the command found in the second field.
|
||||
This command is usually
|
||||
.Xr getty 8 ;
|
||||
|
@ -155,7 +155,7 @@ executes a shell for that user. When this shell
|
|||
dies, either because the user logged out
|
||||
or an abnormal termination occurred (a signal),
|
||||
the
|
||||
.Nm init
|
||||
.Nm
|
||||
program wakes up, deletes the user
|
||||
from the
|
||||
.Xr utmp 5
|
||||
|
@ -164,7 +164,7 @@ file of current users and records the logout in the
|
|||
file.
|
||||
The cycle is
|
||||
then restarted by
|
||||
.Nm init
|
||||
.Nm
|
||||
executing a new
|
||||
.Xr getty
|
||||
for the line.
|
||||
|
@ -176,34 +176,34 @@ may be changed in the
|
|||
file without a reboot by sending the signal
|
||||
.Dv SIGHUP
|
||||
to
|
||||
.Nm init
|
||||
.Nm
|
||||
with the command
|
||||
.Dq Li "kill \-s HUP 1" .
|
||||
On receipt of this signal,
|
||||
.Nm init
|
||||
.Nm
|
||||
re-reads the
|
||||
.Xr ttys
|
||||
file.
|
||||
When a line is turned off in
|
||||
.Xr ttys ,
|
||||
.Nm init
|
||||
.Nm
|
||||
will send a SIGHUP signal to the controlling process
|
||||
for the session associated with the line.
|
||||
For any lines that were previously turned off in the
|
||||
.Xr ttys
|
||||
file and are now on,
|
||||
.Nm init
|
||||
.Nm
|
||||
executes a new
|
||||
.Xr getty
|
||||
to enable a new login.
|
||||
If the getty or window field for a line is changed,
|
||||
the change takes effect at the end of the current
|
||||
login session (e.g., the next time
|
||||
.Nm init
|
||||
.Nm
|
||||
starts a process on the line).
|
||||
If a line is commented out or deleted from
|
||||
.Xr ttys ,
|
||||
.Nm init
|
||||
.Nm
|
||||
will not do anything at all to that line.
|
||||
However, it will complain that the relationship between lines
|
||||
in the
|
||||
|
@ -213,7 +213,7 @@ file and records in the
|
|||
file is out of sync,
|
||||
so this practice is not recommended.
|
||||
.Pp
|
||||
.Nm Init
|
||||
.Nm
|
||||
will terminate multi-user operations and resume single-user mode
|
||||
if sent a terminate
|
||||
.Pq Dv TERM
|
||||
|
@ -225,7 +225,7 @@ hardware or software failure),
|
|||
will not wait for them all to die (which might take forever), but
|
||||
will time out after 30 seconds and print a warning message.
|
||||
.Pp
|
||||
.Nm Init
|
||||
.Nm
|
||||
will cease creating new
|
||||
.Xr getty Ns 's
|
||||
and allow the system to slowly die away, if it is sent a terminal stop
|
||||
|
@ -240,7 +240,7 @@ and
|
|||
.Xr halt 8 .
|
||||
.Pp
|
||||
The role of
|
||||
.Nm init
|
||||
.Nm
|
||||
is so critical that if it dies, the system will reboot itself
|
||||
automatically.
|
||||
If, at bootstrap time, the
|
||||
|
|
Loading…
Reference in New Issue