committed by
William Hubbs
parent
f81bb7e2c4
commit
3054046e18
@@ -76,7 +76,7 @@ Stop all services, kill all processes and reboot the system.
|
||||
.It Fl s , -single
|
||||
Stop all services, kill all processes and move to single user mode.
|
||||
.It Fl w , -write-only
|
||||
Wrrite a wtmp shutdown record and do nothing else.
|
||||
Write a wtmp shutdown record and do nothing else.
|
||||
.El
|
||||
.Sh SEE ALSO
|
||||
.Xr openrc-init 8 ,
|
||||
|
||||
@@ -20,7 +20,7 @@ info
|
||||
.Sh DESCRIPTION
|
||||
.Nm
|
||||
gathers and displays information about the status of services supervised
|
||||
by s6 then runs rc-status to show info about nnormal OpenRC services.
|
||||
by s6 then runs rc-status to show info about normal OpenRC services.
|
||||
.Pp
|
||||
.Sh EXIT STATUS
|
||||
.Nm
|
||||
|
||||
@@ -35,7 +35,7 @@
|
||||
OpenRC uses named runlevels. Rather than editing some obscure
|
||||
file or managing a directory of symlinks,
|
||||
.Nm
|
||||
exists to quickly add or delete services to and from from different runlevels.
|
||||
exists to quickly add or delete services to and from different runlevels.
|
||||
All services must reside in the
|
||||
.Pa /etc/init.d
|
||||
or
|
||||
|
||||
@@ -31,7 +31,7 @@ returns RC_PIDLIST, a structure based on the LIST macro from
|
||||
which contains all the pids found matching the given criteria.
|
||||
If
|
||||
.Fa pid
|
||||
is given then only that pid is returned if it is running. Otherise we check
|
||||
is given then only that pid is returned if it is running. Otherwise we check
|
||||
all instances of
|
||||
.Fa argv
|
||||
with a process name of
|
||||
|
||||
@@ -145,7 +145,7 @@ When
|
||||
.Fa service
|
||||
starts, it starts
|
||||
.Fa service_to_start
|
||||
afterswards as directed by
|
||||
afterwards as directed by
|
||||
.Fn rc_service_schedule_start .
|
||||
.Fn rc_services_scheduled
|
||||
returns a list of services that will be started when
|
||||
|
||||
@@ -193,7 +193,7 @@ If respawn-delay, respawn-max and respawn-period are not set correctly,
|
||||
it is possible to trigger a situation in which the supervisor will
|
||||
infinitely try to respawn a daemon. To avoid this, if you change the
|
||||
values of --respawn-delay, --respawn-max or --respawn-period, always
|
||||
make sure the settings mmake sense. For example, a respawn period of 5
|
||||
make sure the settings make sense. For example, a respawn period of 5
|
||||
seconds with a respawn max of 10 and a respawn delay of 1 second leads
|
||||
to infinite respawning since there can never be 10 respawns within 5
|
||||
seconds.
|
||||
|
||||
Reference in New Issue
Block a user