emo/sysvinit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Applied fixes for markup and spacing in manual pages.

Browse Source 
Patch provided by Mario Blattermann.

Added translation framework (po4a) from Mario Blttermann.
This commit is contained in:
Jesse
2021-12-27 16:14:42 -04:00
parent 933ce33854
commit 92d4b0e74a
24 changed files with 9963 additions and 285 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/Changelog
View File

@ -1,4 +1,8 @@
* Added q and Q flags to synopsis in shutdown manual page.
* Applied fixes for markup and spacing in manual pages.
Patch provided by Mario Blattermann.
* Added translation framework (po4a) from Mario Blttermann.
sysvinit (3.01) released; urgency=low
* Default to showing processes in the uninterruptable state (D).

3
doc/Install
View File

@ -28,6 +28,9 @@ SysV can be built on virtually any Linux system featuring
the GNU C library or musl libc. A C compiler, such as the GNU Compiler
Collection (GCC) or Clang is also required.
On systems which want to provide translated versions of manual pages
the po4a package should be installed.
Here is a list of preferred directories to install the progs & manpages,
this should be done for you automatically when you run "make install"
as the root user, or via sudo, ie "sudo make install".

35
man/bootlogd.8
View File

@ -15,7 +15,7 @@
.\" along with this program; if not, write to the Free Software
.\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
.\"
.TH BOOTLOGD 8 "Jul 21, 2003" "" "Linux System Administrator's Manual"
.TH BOOTLOGD 8 "Jul 21, 2003" "sysvinit @VERSION@" "Linux System Administrator's Manual"
.SH NAME
bootlogd \- record boot messages
.SH SYNOPSIS
@ -26,25 +26,24 @@ bootlogd \- record boot messages
.RB [ \-r ]
.RB [ \-s ]
.RB [ \-v ]
.RB [ " -l logfile " ]
.RB [ " -p pidfile " ]
.RI [ " \fB-l\fP logfile " ]
.RI [ " \fB-p\fP pidfile " ]
.SH DESCRIPTION
\fBBootlogd\fP runs in the background and copies all strings sent to the
\fI/dev/console\fP device to a logfile. If the logfile is not accessible,
\fBbootlogd\fP runs in the background and copies all strings sent to the
\fI/dev/console\fP device to a logfile. If the \fIlogfile\fP is not accessible,
the messages will be kept in memory until it is.
.SH OPTIONS
.IP \fB\-d\fP
Do not fork and run in the background.
.IP \fB\-e\fP
Print escape characters to the boot log file. This turns off filtering of
escape characters and allows tools like GNU Less to see and use colour control
characters (show the log in colour).
escape characters and allows tools like GNU \fBless\fP(1) to see and use
colour control characters (show the log in colour).
.IP \fB\-c\fP
Attempt to write to the logfile even if it does not yet exist.
Without this option,
.B bootlogd
will wait for the logfile to appear before attempting to write to it.
This behavior prevents bootlogd from creating logfiles under mount points.
Without this option, \fBbootlogd\fP will wait for the logfile to appear before
attempting to write to it. This behavior prevents \fBbootlogd\fP from creating
logfiles under mount points.
.IP \fB\-r\fP
If there is an existing logfile called \fIlogfile\fP rename it to
\fIlogfile~\fP unless \fIlogfile~\fP already exists.
@ -61,12 +60,12 @@ Log to this logfile. The default is \fI/var/log/boot\fP.
.IP "\fB\-p\fP \fIpidfile\fP"
Put process-id in this file. The default is no pidfile.
.SH NOTES
bootlogd saves log data which includes control characters. The log is
\fBbootlogd\fP saves log data which includes control characters. The log is
technically a text file, but not very easy for humans to read. To address
this the readbootlog(1) command can be used to display the boot log
this the \fBreadbootlog\fP(1) command can be used to display the boot log
without the control characters.
.SH BUGS
Bootlogd works by redirecting the console output from the console device.
\fBbootlogd\fP works by redirecting the console output from the console device.
(Consequently \fBbootlogd\fP requires PTY support in the kernel configuration.)
It copies that output to the real console device and to a log file.
There is no standard way of ascertaining the real console device
@ -77,6 +76,10 @@ If that syntax is ever changed by the kernel, or a console type is used that
\fBbootlogd\fP does not know about then \fBbootlogd\fP will not work.
.SH AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
.MT miquels@\:cistron\:.nl
Miquel van Smoorenburg
.ME
.SH "SEE ALSO"
.BR dmesg (8), fdatasync (3), readbootlog(1).
.BR dmesg (8),
.BR fdatasync (3),
.BR readbootlog (1)

21
man/fstab-decode.8
View File

@ -17,7 +17,7 @@
.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
.\"
.\" Author: Miloslav Trmac <mitr@redhat.com>
.TH fstab-decode 8 "May 2006"
.TH FSTAB-DECODE 8 "May 2006" "sysvinit @VERSION@" "Linux System Administrator's Manual"
.SH NAME
fstab-decode \- run a command with fstab-encoded arguments
@ -30,11 +30,9 @@ fstab-decode \- run a command with fstab-encoded arguments
decodes escapes (such as newline characters and other whitespace)
in the specified \fIARGUMENT\fRs and uses them to run \fICOMMAND\fR.
The argument escaping uses the same rules as path escaping in
\fB/etc/fstab\fR,
.B /etc/mtab
and \fB/proc/mtab\fR.
\fI/etc/fstab\fR, \fI/etc/mtab\fR and \fI/proc/mtab\fR.
In essence fstab-decode can be used anytime we want to pass multiple
In essence \fBfstab-decode\fR can be used anytime we want to pass multiple
parameters to a command as a list of command line arguments. It turns output
like this:
@ -47,7 +45,7 @@ Into one long list of parameters, "/root /mnt/remote-disk /home". This
can be useful when trying to work with multiple filesystems at once. For
instance, we can use it to unmount multiple NFS shares. This program also
removes whitespace and other characters which might cause programs such
as mount or umount to fail.
as \fBmount\fR(8) or \fBumount\fR(8) to fail.
.SH EXIT STATUS
.B fstab-decode
@ -57,13 +55,12 @@ can't be run.
Otherwise it exits with the status returned by \fICOMMAND\fR.
.SH EXAMPLES
The following example reads \fIfstab\fR, finds all instances of VFAT filesystems
and prints their mount points (argument 2 in the \fIfstab\fR file).
\fBfstab-decode\fR then runs the specified program, \fBumount\fR(8), and passes
it the list of VFAT mountpoints. This unmounts all VFAT partitions.
.nf
The following example reads fstab, finds all instances of VFAT filesystems and
prints their mount points (argument 2 in the fstab file). fstab-decode then runs
the specified program, umount, and passes it the list of VFAT mountpoints.
This unmounts all VFAT partitions.
.B fstab-decode umount $(awk \[aq]$3 == \[dq]vfat\[dq] { print $2 }\[aq] /etc/fstab)
.fi

20
man/halt.8
View File

@ -17,11 +17,11 @@
.\"
.\"{{{}}}
.\"{{{ Title
.TH HALT 8 "Nov 6, 2001" "" "Linux System Administrator's Manual"
.TH HALT 8 "Nov 6, 2001" "sysvinit @VERSION@" "Linux System Administrator's Manual"
.\"}}}
.\"{{{ Name
.SH NAME
halt, reboot, poweroff \- stop the system.
halt, reboot, poweroff \- stop the system
.\"}}}
.\"{{{ Synopsis
.SH SYNOPSIS
@ -61,7 +61,7 @@ normally, \fBshutdown\fP will be invoked instead (with the \fB-h\fP
or \fB-r\fP flag). For more info see the \fBshutdown\fP(8)
manpage.
.PP
The rest of this manpage describes the behaviour in runlevels 0
The rest of this manpage describes the behavior in runlevels 0
and 6, that is when the systems shutdown scripts are being run.
.\"}}}
.\"{{{ Options
@ -77,13 +77,13 @@ Don't write the wtmp record.
.IP \fB\-f\fP
Force halt or reboot, don't call \fBshutdown\fP(8).
.IP \fB\-i\fP
Shut down all network interfaces just before halt or reboot.
Shut down all network interfaces just before \fBhalt\fR or \fBreboot\fR.
Warning: This may not work on interfaces which do not have an IP address
and should ideally be handled by a network manager service.
.IP \fB\-h\fP
Put all hard drives on the system in stand-by mode just before halt or power-off.
.IP \fB\-p\fP
When halting the system, switch off the power. This is the default when halt is
When halting the system, switch off the power. This is the default when \fBhalt\fR is
called as \fBpoweroff\fP.
.\"}}}
.\"{{{ Diagnostics
@ -92,12 +92,12 @@ If you're not the superuser, you will get the message `must be superuser'.
.\"}}}
.\"{{{ Notes
.SH NOTES
Under older \fBsysvinit\fP releases , \fBreboot\fP and \fBhalt\fP should
Under older \fBsysvinit\fP releases, \fBreboot\fP and \fBhalt\fP should
never be called directly. From release 2.74 on \fBhalt\fP and \fBreboot\fP
invoke \fBshutdown\fP(8) if the system is not in runlevel 0 or 6. This
means that if \fBhalt\fP or \fBreboot\fP cannot find out the current
runlevel (for example, when \fI/var/run/utmp\fP hasn't been initialized
correctly and /var/run/runlevel does not exist) \fBshutdown\fP will be called,
correctly and \fI/var/run/runlevel\fR does not exist) \fBshutdown\fP will be called,
which might not be what you want.
Use the \fB-f\fP flag if you want to do a hard \fBhalt\fP or \fBreboot\fP.
.PP
@ -107,14 +107,16 @@ effect of putting the drive in stand-by mode is that the write cache
on the disk is flushed. This is important for IDE drives, since the
kernel doesn't flush the write cache itself before power-off.
.PP
The \fBhalt\fP program uses /proc/ide/hd* to find all IDE disk devices,
The \fBhalt\fP program uses \fI/proc/ide/hd*\fR to find all IDE disk devices,
which means that \fI/proc\fP needs to be mounted when \fBhalt\fP or
\fBpoweroff\fP is called or the \fB-h\fP switch will do nothing.
.PP
.\"}}}
.\"{{{ Author
.SH AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
.MT miquels@\:cistron\:.nl
Miquel van Smoorenburg
.ME
.\"}}}
.\"{{{ See also
.SH "SEE ALSO"

104
man/init.8
View File

@ -17,7 +17,7 @@
.\"
.\"{{{}}}
.\"{{{ Title
.TH INIT 8 "29 Jul 2004" "" "Linux System Administrator's Manual"
.TH INIT 8 "29 Jul 2004" "sysvinit @VERSION@" "Linux System Administrator's Manual"
.\"}}}
.\"{{{ Name
.SH NAME
@ -46,19 +46,19 @@ init, telinit \- process control initialization
.SH DESCRIPTION
.\"{{{ init
.SS Init
.B Init
.B init
is the parent of all processes. Its primary role is to create processes
from a script stored in the file \fB/etc/inittab\fP (see
\fIinittab\fP(5)). This file usually has entries which cause \fBinit\fP
to spawn \fBgetty\fPs on each line that users can log in. It also
from a script stored in the file \fI/etc/inittab\fR (see
\fBinittab\fR(5)). This file usually has entries which cause \fBinit\fR
to spawn \fBgetty\fRs on each line that users can log in. It also
controls autonomous processes required by any particular system.
.PP
.\"{{{ Runlevels
.SH RUNLEVELS
A \fIrunlevel\fP is a software configuration of the system which allows
A \fIrunlevel\fR is a software configuration of the system which allows
only a selected group of processes to exist. The processes spawned by
\fBinit\fP for each of these runlevels are defined in the
\fB/etc/inittab\fP file. \fBInit\fP can be in one of eight runlevels:
\fBinit\fR for each of these runlevels are defined in the
\fI/etc/inittab\fR file. \fBinit\fR can be in one of eight runlevels:
\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP). The runlevel is
changed by having a privileged user run \fBtelinit\fP, which sends
appropriate signals to \fBinit\fP, telling it which runlevel to change
@ -92,16 +92,16 @@ Internally they are aliases for the same runlevel.
.PP
.SH BOOTING
After \fBinit\fP is invoked as the last step of the kernel boot sequence,
it looks for the file \fB/etc/inittab\fP to see if there is an entry of the
type \fBinitdefault\fP (see \fIinittab\fP(5)). The \fBinitdefault\fP entry
it looks for the file \fI/etc/inittab\fP to see if there is an entry of the
type \fBinitdefault\fP (see \fBinittab\fR(5)). The \fBinitdefault\fP entry
determines the initial runlevel of the system. If there is no such
entry (or no \fB/etc/inittab\fP at all), a runlevel must be
entry (or no \fI/etc/inittab\fR at all), a runlevel must be
entered at the system console.
.PP
Runlevel \fBS\fP or \fBs\fP initialize the system
and do not require an \fB/etc/inittab\fP file.
and do not require an \fI/etc/inittab\fP file.
.PP
In single user mode, \fB/sbin/sulogin\fP is invoked on \fB/dev/console\fP.
In single user mode, \fB/sbin/sulogin\fP is invoked on \fI/dev/console\fP.
.PP
When entering single user mode, \fBinit\fP initializes the consoles
\fBstty\fP settings to sane values. Clocal mode is set. Hardware
@ -117,21 +117,21 @@ When starting a new process, \fBinit\fP first checks whether the file
start the process.
.PP
Each time a child terminates, \fBinit\fP records the fact and the reason
it died in \fB/var/run/utmp\fP and \fB/var/log/wtmp\fP,
it died in \fI/var/run/utmp\fP and \fI/var/log/wtmp\fP,
provided that these files exist.
.SH CHANGING RUNLEVELS
After it has spawned all of the processes specified, \fBinit\fP waits
for one of its descendant processes to die, a powerfail signal, or until
it is signaled by \fBtelinit\fP to change the system's runlevel.
When one of the above three conditions occurs, it re-examines
the \fB/etc/inittab\fP file. New entries can be added to this file at
the \fI/etc/inittab\fP file. New entries can be added to this file at
any time. However, \fBinit\fP still waits for one of the above three
conditions to occur. To provide for an instantaneous response, the
\fBtelinit Q\fP or \fBq\fP command can wake up \fBinit\fP to re-examine (reload) the
\fB/etc/inittab\fP file.
\fI/etc/inittab\fP file.
.PP
If \fBinit\fP is not in single user mode and receives a powerfail
signal (SIGPWR), it reads the file \fB/etc/powerstatus\fP. It then starts
signal (SIGPWR), it reads the file \fI/etc/powerstatus\fP. It then starts
a command based on the contents of this file:
.IP F(AIL)
Power is failing, UPS is providing the power. Execute the \fBpowerwait\fP
@ -142,19 +142,19 @@ The power has been restored, execute the \fBpowerokwait\fP entries.
The power is failing and the UPS has a low battery. Execute the
\fBpowerfailnow\fP entries.
.PP
If /etc/powerstatus doesn't exist or contains anything else then the
letters \fBF\fP, \fBO\fP or \fBL\fP, init will behave as if it has read
If \fI/etc/powerstatus\fR doesn't exist or contains anything else then the
letters \fBF\fP, \fBO\fP or \fBL\fP, \fBinit\fR will behave as if it has read
the letter \fBF\fP.
.PP
Usage of \fBSIGPWR\fP and \fB/etc/powerstatus\fP is discouraged. Someone
wanting to interact with \fBinit\fP should use the \fB/run/initctl\fP
control channel - see the initctl manual page for more documentation
Usage of \fBSIGPWR\fP and \fI/etc/powerstatus\fP is discouraged. Someone
wanting to interact with \fBinit\fP should use the \fI/run/initctl\fP
control channel - see the \fBinitctl\fR(5) manual page for more documentation
about this.
.PP
When \fBinit\fP is requested to change the runlevel, it sends the
warning signal \s-1\fBSIGTERM\fP\s0 to all processes that are undefined
warning signal \fBSIGTERM\fP to all processes that are undefined
in the new runlevel. It then waits 3 seconds before forcibly
terminating these processes via the \s-1\fBSIGKILL\fP\s0 signal.
terminating these processes via the \fBSIGKILL\fP signal.
Note that \fBinit\fP assumes that all these processes (and their
descendants) remain in the same process group which \fBinit\fP
originally created for them. If any process changes its process group
@ -167,23 +167,23 @@ be terminated separately.
one-character argument and signals \fBinit\fP to perform the appropriate
action. The following arguments serve as directives to
\fBtelinit\fP:
.IP "\fB0\fP,\fB1\fP,\fB2\fP,\fB3\fP,\fB4\fP,\fB5\fP or \fB6\fP"
.IP "\fB0\fP, \fB1\fP, \fB2\fP, \fB3\fP, \fB4\fP, \fB5\fP or \fB6\fP"
tell \fBinit\fP to switch to the specified run level.
.IP \fBa\fP,\fBb\fP,\fBc\fP