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

Rework the manpages into mdoc format for easier maintainence

Browse Source
This commit is contained in:
Roy Marples 2007-12-17 10:14:54 +00:00
parent 33dac46299
commit 4a4f808a0f
4 changed files with 272 additions and 306 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/Makefile
View File

@ -1,5 +1,5 @@
DIR = /usr/share/man/man8 DIR = /usr/share/man/man8
CONF = rc-status.8 rc-update.8 start-stop-daemon.8 INC = rc-status.8 rc-update.8 start-stop-daemon.8
TOPDIR = .. TOPDIR = ..
include $(TOPDIR)/default.mk include $(TOPDIR)/default.mk

92
man/rc-status.8
View File

@ -1,33 +1,61 @@
.TH "OPENRC" "8" "Nov 2007" "openrc" "openrc" .\" Copyright 2007 Roy Marples
.SH NAME .\" All rights reserved
rc-status \- show status info about runlevels .\"
.SH SYNOPSIS .\" Redistribution and use in source and binary forms, with or without
\fBrc-status\fR \fI[command [runlevel]]\fR .\" modification, are permitted provided that the following conditions
.SH DESCRIPTION .\" are met:
\fBrc-status\fR gathers and displays information about the status of init .\" 1. Redistributions of source code must retain the above copyright
scripts in different runlevels. The default behavior is to show information .\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.Dd Dec 15, 2007
.Dt RC-STATUS 8 SMM
.Os OpenRC
.Sh NAME
.Nm rc-status
.Nd show status info about runlevels
.Sh SYNOPSIS
.Nm
.Op Fl alsuC
.Op Ar runlevel
.Sh DESCRIPTION
.Nm
gathers and displays information about the status of services
in different runlevels. The default behavior is to show information
about the current runlevel, but any runlevel can be quickly examined. about the current runlevel, but any runlevel can be quickly examined.
directory. They must also conform to the OpenRC runscript standard. .Pp
.SH OPTIONS The options are as follows:
.TP .Bl -tag -width ".Fl test , test string"
\fB\-\-all (\-a)\fR .It Fl a , -all
Show all runlevels and their services Show all runlevels and their services.
.TP .It Fl l , -list
\fB\-\-list (\-l)\fR List all defined runlevels.
List all defined runlevels .It Fl s , -servicelist
.TP Show all services.
\fB\-\-nocolor (\-nc)\fR .It Fl u , -unused
Disable color output Show services not assigned to any runlevel.
.TP .It Fl C , -nocolor
\fB\-\-servicelist (\-s)\fR Disable color output.
Show all services .It Ar runlevel
.TP Show information only for the named
\fB\-\-unused (\-u)\fR .Ar runlevel .
Show services not assigned to any runlevel .El
.TP .Sh SEE ALSO
\fB[runlevel]\fR .Xr rc 8 ,
Show information only for the named \fBrunlevel\fR .Xr rc-update 8
.SH "SEE ALSO" .Sh AUTHORS
.BR rc-update (8) .An "Roy Marples" Aq roy@marples.name
.SH AUTHORS
Mike Frysinger <vapier@gentoo.org>

117
man/rc-update.8
View File

@ -1,39 +1,80 @@
.TH "OPENRC" "8" "Nov 2007" "openrc" "openrc" .\" Copyright 2007 Roy Marples
.SH NAME .\" All rights reserved
rc-update \- add and remove init scripts to a runlevel .\"
.SH SYNOPSIS .\" Redistribution and use in source and binary forms, with or without
\fBrc-update\fR \fIadd\fR \fIscript\fR \fI<runlevels>\fR .\" modification, are permitted provided that the following conditions
.br .\" are met:
\fBrc-update\fR \fIdel\fR \fIscript\fR \fI[runlevels]\fR .\" 1. Redistributions of source code must retain the above copyright
.br .\" notice, this list of conditions and the following disclaimer.
\fBrc-update\fR \fIshow\fR \fI[\-\-verbose]\fR \fI[runlevels]\fR .\" 2. Redistributions in binary form must reproduce the above copyright
.SH DESCRIPTION .\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.Dd Dec 15, 2007
.Dt RC-UPDATE 8 SMM
.Os OpenRC
.Sh NAME
.Nm rc-update
.Nd add and remove services to and from a runlevel
.Sh SYNOPSIS
.Nm
.Fl a , -add
.Ar service
.Op Ar runlevel ...
.Nm
.Fl d , -delete
.Ar service
.Op Ar runlevel ...
.Nm
.Fl s , -show
.Op Fl v , -verbose
.Op Ar runlevel ...
.Sh DESCRIPTION
OpenRC uses named runlevels. Rather than editing some obscure OpenRC uses named runlevels. Rather than editing some obscure
file or managing a directory of symlinks, \fBrc-update\fR exists to quickly file or managing a directory of symlinks,
add or delete init scripts from different runlevels. .Nm
exists to quickly add or delete services to and from from different runlevels.
All scripts specified with this utility must reside in the \fI/etc/init.d\fR All services must reside in the
directory. They must also conform to the OpenRC runscript standard. .Pa /etc/init.d
.SH OPTIONS or
.TP .Pa /usr/local/etc/init.d
\fBadd (\-a)\fR \fIscript\fR \fI<runlevels>\fR directories. They must also conform to the OpenRC runscript standard.
Add the specified \fIinit script\fR to the specified \fIrunlevels\fR. You .Pp
must specify at least one runlevel. .Bl -tag -width "Fl a , -delete service"
.It Fl a , -add Ar service
Example: rc-update add net.eth0 default Add the
.TP .Ar service
\fBdel (\-d)\fR \fIscript\fR \fI[runlevels]\fR to the
Delete the specified \fIinit script\fR from the specified \fIrunlevels\fR. .Ar runlevel
If you do not specify the \fIrunlevels\fR from which to delete, the script or the current one if none given.
will be removed from all exists runlevels. Services added to the boot runlevel must exist in
.Pa /etc/init.d .
Example: rc-update del sysklogd .It Fl d , -delete Ar service
.TP Delete the
\fBshow (\-s)\fR \fI[\-v|\-\-verbose]\fR \fI[runlevels]\fR .Ar service
Show all enabled scripts and the runlevels they belong to. If you specify from the
\fIrunlevels\fR to show, then only those will be included in the output. To .Ar runlevel
view all init scripts, run with the \fI\-\-verbose\fR option. or the current one if none given.
.It Fl s , -show
Example: rc-update show Show all enabled services and the runlevels they belong to. If you specify
.SH "SEE ALSO" runlevels to show, then only those will be included in the output.
.BR rc-status (8) .It Fl v , -verbose
Show all services.
.El
.Sh SEE ALSO
.Xr rc 8 ,
.Xr rc-status 8
.Sh AUTHORS
.An "Roy Marples" Aq roy@marples.name

367
man/start-stop-daemon.8
View File

@ -1,237 +1,134 @@
.TH "OPENRC" "13" "Nov 2007" "openrc" "openrc" .\" Copyright 2007 Roy Marples
.SH NAME .\" All rights reserved
start\-stop\-daemon \- start and stop system daemon programs .\"
.SH SYNOPSIS .\" Redistribution and use in source and binary forms, with or without
.B start-stop-daemon .\" modification, are permitted provided that the following conditions
.BR -S | --start .\" are met:
.IR options .\" 1. Redistributions of source code must retain the above copyright
.RB [ \-\- ] .\" notice, this list of conditions and the following disclaimer.
.IR arguments .\" 2. Redistributions in binary form must reproduce the above copyright
.HP .\" notice, this list of conditions and the following disclaimer in the
.B start-stop-daemon .\" documentation and/or other materials provided with the distribution.
.BR -K | --stop .\"
.IR options .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
.HP .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.B start-stop-daemon .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.BR -s | --signal .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
.IR options .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.HP .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.B start-stop-daemon .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.BR -H | --help .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.HP .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.B start-stop-daemon .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.BR -V | --version .\" SUCH DAMAGE.
.SH DESCRIPTION .\"
.B start\-stop\-daemon .Dd Dec 15, 2007
is used to control the creation and termination of system-level processes. .Dt START-STOP-DAEMON 8 SMM
Using the .Os OpenRC
.BR --exec ", " --pidfile ", " --user ", and " --name " options," .Sh NAME
.B start\-stop\-daemon .Nm start-stop-daemon
can be configured to find existing instances of a running process. .Nd ensures that daemons start and stop
.Sh SYNOPSIS
With .Nm
.BR --start , .Fl S , -start
.B start\-stop\-daemon .Ar daemon
checks for the existence of a specified process. .Op Fl -
If such a process exists, .Op Ar arguments
.B start\-stop\-daemon .Nm
does nothing, and exits with error status 1. .Fl K , -stop
If such a process does not exist, it starts an .Ar daemon
instance, using the executable specified by .Nm
.BR --exec . .Fl s , -signal
Any arguments given after .Ar signal
.BR -- .Ar daemon
on the command line are passed unmodified to the program being .Sh DESCRIPTION
started. .Nm
.B start\-stop\-daemon provides a consistent method of starting, stopping and signalling daemons.
pauses for a little bit then checks the daemon is still running as badly If a daemon cannot background by itself, nor create a pidfile,
written ones like to fork early and then bail on a error in their config. .Nm
As such it may be necessary to use the --name parameter if the daemon in can do it for the daemon in a secure fashion.
question is not a C program, ie a script. Once started, we store how we .Nm
are called in \fBrc\fR if called from an init script. also ensures that a daemon really has started by checking to see if it still
exists for a short time after it has started. This is because some badly
With written daemons like to daemonize before checking their configuration, doing
.BR --stop , sanity checks, etc. Likewise,
.B start\-stop\-daemon .Nm
also checks for the existence of a specified process. ensures that a daemon really stops as well, again by using the information
If such a process exists, above to ensure that it's not running.
.B start\-stop\-daemon .Pp
sends it the signal specified by
.BR --signal ,
and exits with error status 0.
If such a process does not exist, or there was an error stopping it
.B start\-stop\-daemon
exits with error status 1. If
.BR --test
is specified then we just send the signal and not the schedule. If
.BR --oknodo
is specified then we don't remove the daemon information from
.BR rc. If neither
.BR --test
or
.BR --okndo
are specified then we kill signalling and waiting according to our
schedule specified by
.BR --retry
until we timeout the process(es) exited. If we didn't timeout then
we remove our daemon information from rc.
With
.BR --signal ,
.B start\-stop\-daemon
also checks for the existence of a specified process.
If such a process exists,
.B start\-stop\-daemon
sends it the signal specified and exits with error status 0.
If such a process does not exist, or there was an error stopping it
.B start\-stop\-daemon
exits with error status 1. No futher action is taken
.SH OPTIONS
.TP
\fB-x\fP|\fB--exec\fP \fIexecutable\fP
Check for processes that are instances of this executable.
.TP
\fB-p\fP|\fB--pidfile\fP \fIpid-file\fP
Check for processes whose process-id is specified in
.I pid-file.
.TP
\fB-u\fP|\fB--user\fP \fIusername\fP|\fIuid\fP
Check for processes owned by the user specified by
.I username
or
.I uid.
.TP
\fB-n\fP|\fB--name\fP \fIprocess-name\fP
Check for processes with the name
.I process-name
.TP
\fB-s\fP|\fB--signal\fP \fIsignal\fP
With
.BR --stop
, specifies the signal to send to processes being stopped (default SIGTERM).
.TP
\fB-R\fP|\fB--retry\fP \fItimeout\fP|\fIschedule\fP
With
.BR --stop ,
specifies that
.B start-stop-daemon
is to check whether the process(es)
do finish. It will check repeatedly whether any matching processes
are running, until none are. If the processes do not exit it will
then take further action as determined by the schedule.
If If
.I timeout .Nm
is specified instead of is used in an OpenRC service, then OpenRC can in turn check to see if the
.I schedule daemon is still running. If not, then the service is marked as crashed.
then the schedule .Pp
.IB signal / timeout Here are the options to specify the daemon and how it should start or stop:
is used, where .Bl -tag -width indent
.I signal .It Fl x , -exec Ar daemon
is the signal specified with The daemon we start or stop.
.BR --signal . .It Fl p , -pidfile Ar pidfile
When starting, we expect the daemon to create a valid pidfile within a
.I schedule reasonable amount of time. When stopping we only stop the pid(s) listed in
is a list of at least two items separated by slashes the pidfile.
.RB ( / ); .It Fl n , -name Ar name
each item may be For whatever reason, some daemons don't create pidfiles or change their
.BI - signal-number process name. You can specify name here to be the process name to stop.
or [\fB\-\fP]\fIsignal-name\fP, You may need to use this for interpreted daemons using languages such as
which means to send that signal, perl, ruby, shell, etc.
or .It Fl u , -user Ar user Ns Op : Ns Ar group
.IR timeout , Start the daemon as the user and update $HOME accordingly or stop daemons
which means to wait that many seconds for processes to owned by the user. You can optionally append a groupname here also.
exit, .It Fl t , -test
or Print the action(s) that would be taken, but don't actually do anything.
.BR forever , The return value is set as if the command was taken and worked.
which means to repeat the rest of the schedule forever if .El
necessary. .Pp
These options are only used for starting daemons:
If the end of the schedule is reached and .Bl -tag -width indent
.BR forever .It Fl b , -background
is not specified, then Force the daemon into the background. Some daemons don't create pidfiles, so a
.B start-stop-daemon good trick is to get the daemon to run in the foreground, and use the this
exits with error status 2. option along with
If a schedule is specified, then any signal specified .Fl m , -make-pidfile
with to create a working pidfile.
.B --signal .It Fl d , -chdir Ar path
is ignored. chdir to this directory before starting the daemon.
.TP .It Fl r , -chroot Ar path
.BR -t | --test chroot to this directory before starting the daemon. All other paths, such
Print actions that would be taken and set appropriate return value, as the path to the daemon, chdir and pidfile, should be relative to the chroot.
but take no action. .It Fl g , -group Ar group
.TP Start the daemon as in the group.
.BR -o | --oknodo .It Fl m , -make-pidfile
Used for sending signals to a running daemon but not expecting it to stop. Saves the pid of the daemon in the file specified by the
In this version you can don't need --oknodo if you don't use --stop either. .Fl p , -pidfile
.TP option. Only useful when used with daemons that run in the foreground and
.BR -q | --quiet forced into the background with the
Do not print informational messages; only display error messages. .Fl -b , -background
.TP
\fB-c\fP|\fB--chuid\fP \fIusername\fR|\fIuid\fP
Change to this username/uid before starting the process. You can also
specify a group by appending a
.BR : ,
then the group or gid in the same way
as you would for the `chown' command (\fIuser\fP\fB:\fP\fIgroup\fP).
When using this option
you must realize that the primary and supplemental groups are set as well,
even if the
.B --group
option is not specified. The
.B --group
option is only for
groups that the user isn't normally a member of (like adding per/process
group membership for generic users like
.BR nobody ).
.TP
\fB-r\fP|\fB--chroot\fP \fIroot\fP
Chdir and chroot to
.I root
before starting the process. Please note that the pidfile is also written
after the chroot.
.TP
.BR -b | --background
Typically used with programs that don't detach on their own. This option
will force
.B start-stop-daemon
to fork before starting the process, and force it into the background.
.TP
\fB-1\fP|\fB--stdout\fP \fIlogfile\fP
Redirect the standard output of the process to \fIlogfile\fP when started with
\fB--background\fP. Must be an absolute pathname, but relative to the
\fIpath\fP optionally given with \fB--chroot\fP.
Hint: The \fIlogfile\fP can also be a named pipe.
.TP
\fB-2\fP|\fB--stderr\fP \fIlogfile\fP
The same thing as \fB--stdout\fP but with the standard error output.
.TP
.BR -N | --nicelevel
This alters the prority of the process before starting it. This can also be set
by the environment variable \fBSSD_NICELEVEL\fR.
.TP
.BR -m | --make-pidfile
Used when starting a program that does not create its own pid file. This
option will make
.B start-stop-daemon
create the file referenced with
.B --pidfile
and place the pid into it just before executing the process. Note, it will
not be removed when stopping the program.
.B NOTE:
This feature may not work in all cases. Most notably when the program
being executed forks from its main process. Because of this it is usually
only useful when combined with the
.B --background
option. option.
.TP .It Fl n , -nice Ar level
.BR -v | --verbose Modifies the scheduling priority of the daemon.
Print verbose informational messages. .It Fl 1 , -stdout Ar logfile
.TP Redirect the standard output of the process to logfile when started with
.BR -H | --help .Fl background .
Print help information; then exit. Must be an absolute pathname, but relative to the path optionally given with
.TP .Fl r , -chroot .
.BR -V | --version The logfile can also be a named pipe.
Print version information; then exit. .It Fl 2 , -stderr Ar logfile
The same thing as
.Fl 1 , -stdout
but with the standard error output.
.El
.Pp
These options are only used for stopping daemons:
.Bl -tag -width indent
.It Fl R , -retry Ar timeout | Ar signal Ns / Ns Ar timeout
You can either specify a timeout or a multiple signal/timeout pairs as a
stopping schedule.
If not specified then a default value of SIGTERM/5 is
assumed.
.El
.Sh SEE ALSO
.Xr chdir 2 ,
.Xr chroot 2 ,
.Xr nice 2
.Sh AUTHORS
.An "Roy Marples" Aq roy@marples.name