mirror of https://github.com/GnoConsortium/gno.git
added man pages for init, syslogd
This commit is contained in:
gdr
parent
1e7233ff6a
commit
cb5fd8e82d
|
|
@ -0,0 +1,189 @@
|
|||
.\"
|
||||
.\" $Id: init.8,v 1.1 1997/02/28 05:12:12 gdr Exp $
|
||||
.\"
|
||||
.TH INIT 8 "27 October 1993" GNO "System Administration"
|
||||
.SH NAME
|
||||
\fBinit\fR \- start and kill processes
|
||||
.SH DESCRIPTION
|
||||
.B init
|
||||
is the component of the UNIX operating system that is responsible
|
||||
for creating processes once the system has finished booting and for
|
||||
maintaining those processes, including killing them.
|
||||
.sp
|
||||
At any time, the system is in one of 12 states or run levels. At
|
||||
each run level, a different group of processes is allowed to run.
|
||||
Generally, when the run level changes, init kills the processes which
|
||||
it created under the old run level, and creates a new set for the new
|
||||
run level.
|
||||
.sp
|
||||
Run levels are identified with single characters in the set
|
||||
.RB [ bs0123456789 ].
|
||||
.BR B
|
||||
and
|
||||
.BR S
|
||||
are also accepted as equivalents to
|
||||
.BR b
|
||||
and
|
||||
.BR s .
|
||||
Some of these run levels have special meaning and are listed below.
|
||||
Except for
|
||||
.BR b ,
|
||||
all run levels can have their meaning changed via
|
||||
.IR runl
|
||||
commands in
|
||||
.BR /etc/inittab .
|
||||
.sp
|
||||
Except for levels
|
||||
.BR 0 ,
|
||||
.BR 5
|
||||
and
|
||||
.BR 6 ,
|
||||
the actual state of the machine after
|
||||
.B init
|
||||
switches to a level is completely defined by the processes which run,
|
||||
which are configurable in
|
||||
.BR /etc/inittab .
|
||||
It is therefore possible to use all but those three run levels for
|
||||
purposes other than their intended one. Their meaning as described
|
||||
here are the conventional meaning. It is encouraged that the
|
||||
conventions be followed.
|
||||
.IP "\fBb\fR (boot)"
|
||||
This is the run level that is selected by default. Any
|
||||
initialization processes should be run under this level.
|
||||
By default, init switches to run level
|
||||
.BR s
|
||||
(single user) after
|
||||
starting processes at this level. The
|
||||
.B bootlevel
|
||||
command in
|
||||
.I /etc/rchost
|
||||
may be used to modify this behavior.
|
||||
.IP \fB0\fR
|
||||
This is the system shutdown level. Switching to this level will cause
|
||||
the system to shut down after any level
|
||||
.BR 0
|
||||
processes have been run.
|
||||
.IP \fB1\fR
|
||||
This run level is defined as the administration state.
|
||||
.IP "\fB2\fR, \fB3\fR, \fB4\fR"
|
||||
These are multi user run levels.
|
||||
Level
|
||||
.BR 2
|
||||
is standard. Level
|
||||
.BR 3
|
||||
is multi user with networking, and level
|
||||
.BR 4
|
||||
is an alternate multi user set up.
|
||||
.IP \fB5\fR
|
||||
Under UNIX, this is the firmware monitor run level. Under GNO, switching
|
||||
to this level causes GNO to quit. The disparity arises from the fact
|
||||
that there is no such thing as quitting UNIX.
|
||||
.IP \fB6\fR
|
||||
Switching to this level causes the system to reboot.
|
||||
.IP \fBs\fR
|
||||
This is the single user run level.
|
||||
.IP "\fB7\fR, \fB8\fR"
|
||||
These are local run levels. Any local terminals are active, as well as
|
||||
any local area networks (level
|
||||
.BR 8 ),
|
||||
but no dialups are active and no
|
||||
modem based networking is available.
|
||||
.IP \fB9\fR
|
||||
This level is undefined.
|
||||
.SH SIGNALS
|
||||
The following signals can be sent to init to force certain conditions.
|
||||
Note that these are intended as low level commands;
|
||||
.BR init (1)
|
||||
should be used to issue these signals.
|
||||
.IP \fBSIGHUP\fR
|
||||
Causes init to reread
|
||||
.BR /etc/inittab ,
|
||||
kill processes that have been removed from it, and start processes that
|
||||
were newly added.
|
||||
.sp 1
|
||||
.BR init
|
||||
depends on the process names (see
|
||||
.BR inittab (5))
|
||||
to compare the old copy of the table with the new one.
|
||||
.IP \fBSIGTERM\fR
|
||||
Causes
|
||||
.BR init
|
||||
to switch to the kill default run level. This is
|
||||
.BR 0
|
||||
unless it is changed in
|
||||
.BR /etc/inittab .
|
||||
Normally, the effect is a system shutdown.
|
||||
.IP \fBSIGUSR1\fR
|
||||
Causes init to try to receive a message (see
|
||||
.BR procrecv (2))
|
||||
and act on it. The message is typically sent by
|
||||
.BR init (1)
|
||||
and contains status inquiries or run level change requests.
|
||||
.IP \fBSIGUSR2\fR
|
||||
Causes
|
||||
.BR init
|
||||
to exit its
|
||||
.BR sigpause (2)
|
||||
and check for any pending events (which is useful if a timing bug has caused
|
||||
.BR init
|
||||
to go to sleep while it had pending events).
|
||||
.SH NOTES
|
||||
Under real UNIX, there are fewer run levels.
|
||||
.LP
|
||||
When switching to some run levels,
|
||||
.BR init
|
||||
automatically issues a
|
||||
.I runl
|
||||
command to carry out the apropriate action for that run level.
|
||||
This action can be overridden with another
|
||||
.I runl
|
||||
command, possibly
|
||||
.BR n
|
||||
to cancel any special action at all.
|
||||
.LP
|
||||
If
|
||||
.BR init
|
||||
becomes idle and has no children, it switch to the idle run level,
|
||||
which is
|
||||
.BR 5
|
||||
by default.
|
||||
.LP
|
||||
If a LOG_EMERG message is received by
|
||||
.BR syslogd (8),
|
||||
.BR init
|
||||
will switch to the panic run level,
|
||||
.BR 6
|
||||
by default.
|
||||
.LP
|
||||
When a child of
|
||||
.BR init
|
||||
dies, any entry it has in the
|
||||
.BR utmp (5)
|
||||
database will be removed before any other action is taken. Also, stray bogus
|
||||
entries are removed whenever they are noticed.
|
||||
.LP
|
||||
At startup time,
|
||||
.BR init
|
||||
tries to read the file
|
||||
.BR /etc/rchost
|
||||
and set certain system globals according to the information in that file.
|
||||
.SH FILES
|
||||
.BR /etc/inittab
|
||||
.br
|
||||
.BR /usr/sbin/initd
|
||||
.br
|
||||
.BR /var/adm/utmp
|
||||
.br
|
||||
.BR /var/adm/wtmp
|
||||
.br
|
||||
.BR /etc/rchost
|
||||
.SH "SEE ALSO"
|
||||
.LP
|
||||
.BR init (1),
|
||||
.BR inittab (5),
|
||||
.BR rchost (5),
|
||||
.BR utmp (5),
|
||||
.BR getty (8),
|
||||
.BR syslogd (8)
|
||||
.SH AUTHOR
|
||||
Phillip Vandry, <vandry@cam.org>
|
||||
|
|
@ -0,0 +1,93 @@
|
|||
.\"
|
||||
.\" $Id: syslogd.8,v 1.1 1997/02/28 05:12:12 gdr Exp $
|
||||
.\"
|
||||
.TH SYSLOGD 8 "27 October 1993" GNO "System Administration"
|
||||
.SH NAME
|
||||
\fBsyslogd\fR \- log system messages
|
||||
.SH DESCRIPTION
|
||||
.LP
|
||||
.B syslogd
|
||||
is responsible for receiving system log messages and routing them to
|
||||
the apropriate file or terminal based on the type of message.
|
||||
.LP
|
||||
Messages are passed to
|
||||
.BR syslogd
|
||||
using
|
||||
.BR syslog (2).
|
||||
Each message has a
|
||||
.I facility
|
||||
and a
|
||||
.IR priority .
|
||||
The
|
||||
.IR facility
|
||||
identifies which part of the system issued the message. The
|
||||
.IR priority
|
||||
indicates the severity of the message. The codes for both can be found in
|
||||
the header file <sys/syslog.h>.
|
||||
.LP
|
||||
If
|
||||
.BR syslogd
|
||||
receives a message with priority
|
||||
.BR LOG_EMERG ,
|
||||
meaning the system is unusable, it will flag a panic.
|
||||
.BR init (8)
|
||||
will then take additional action, such as rebooting.
|
||||
.LP
|
||||
.B syslogd
|
||||
is automatically started by
|
||||
.BR init (8)
|
||||
and is restarted if it is killed. If
|
||||
.BR syslogd
|
||||
is killed and restarted, the port id will not change.
|
||||
.LP
|
||||
Killing
|
||||
.BR syslogd
|
||||
has the effect that the configuration file will be reread.
|
||||
.SH CONFIGURATION
|
||||
At startup,
|
||||
.BR syslogd
|
||||
reads the file
|
||||
.BR /etc/syslog.conf .
|
||||
The format of each line in this file is:
|
||||
.nf
|
||||
|
||||
\fIfacility\fR.\fIpriority\fR \fIdestination\fR,...
|
||||
|
||||
.fi
|
||||
where either or both of
|
||||
.I facility
|
||||
and
|
||||
.IR priority
|
||||
can be
|
||||
.BR * ,
|
||||
meaning any value.
|
||||
.IR destination
|
||||
is either the full pathname of a file where the message should be saved, or a
|
||||
user name to whom messages should be reported.
|
||||
.LP
|
||||
The default configuration is equivalent to the following syslog.conf
|
||||
file:
|
||||
.nf
|
||||
|
||||
*.* /var/adm/syslog,root
|
||||
.fi
|
||||
.SH BUGS
|
||||
.BR syslog (2)
|
||||
must wait for the message it sends to be received by
|
||||
.BR syslogd
|
||||
before returning. Otherwise, the calling process might exit and the memory
|
||||
which contained the message would be disposed of if
|
||||
.BR syslogd
|
||||
had not yet transfered the memory's ownership to itself.
|
||||
.LP
|
||||
If a user is logged on multiple times, he or she will only receive
|
||||
syslog messages in the first location (in the order of
|
||||
.BR /etc/ttys ).
|
||||
.SH FILES
|
||||
.BR /etc/syslog.conf
|
||||
.SH "SEE ALSO"
|
||||
.LP
|
||||
.BR syslog (2),
|
||||
.BR init (8)
|
||||
.SH AUTHOR
|
||||
Phillip Vandry, <vandry@cam.org>
|
||||
Loading…
Reference in New Issue