d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

man(7) -> mdoc(7).

Browse Source
This commit is contained in:
ru 2001-01-16 17:29:42 +00:00
parent b72a3c78cc
commit 625daed24d
2 changed files with 31 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
usr.sbin/named.reload/named.reload.8
View File

@ -54,17 +54,23 @@
.\" from hostname.7 6.4 (Berkeley) 1/16/90
.\" $FreeBSD$
.\"
.TH @INDOT_U@NAMED.RELOAD @SYS_OPS_EXT_U@ "June 26, 1993"
.UC 5
.SH NAME
@INDOT@named.reload \- cause the name server to synchronize its database
.SH DESCRIPTION
This command sends a \s-1SIGHUP\s+1 to the running name server. This
.Dd June 26, 1993
.Dt @INDOT_U@NAMED.RELOAD @SYS_OPS_EXT_U@
.Os
.Sh NAME
.Nm @INDOT@named.reload
.Nd "cause the name server to synchronize its database"
.Sh DESCRIPTION
This command sends a
.Dv SIGHUP
to the running name server.
This
signal is documented in
.IR named (@SYS_OPS_EXT@).
.SH BUGS
.Xr named @SYS_OPS_EXT@ .
.Sh BUGS
Does not check to see if the name server is actually running, and could
use a stale PID cache file which may result in the death of an unrelated
process.
.SH SEE ALSO
@INDOT@named(@SYS_OPS_EXT@), @INDOT@named.restart(@SYS_OPS_EXT@)
.Sh SEE ALSO
.Xr @INDOT@named @SYS_OPS_EXT@ ,
.Xr @INDOT@named.restart @SYS_OPS_EXT@

25
usr.sbin/named.restart/named.restart.8
View File

@ -54,21 +54,26 @@
.\" from hostname.7 6.4 (Berkeley) 1/16/90
.\" $FreeBSD$
.\"
.TH @INDOT_U@NAMED.RESTART @SYS_OPS_EXT_U@ "June 26, 1993"
.UC 5
.SH NAME
@INDOT@named.restart \- stop and restart the name server
.SH DESCRIPTION
This command sends a \s-1SIGKILL\s+1 to the running name server and then
.Dd June 26, 1993
.Dt @INDOT_U@NAMED.RESTART @SYS_OPS_EXT_U@
.Os
.Sh NAME
.Nm @INDOT@named.restart
.Nd "stop and restart the name server"
.Sh DESCRIPTION
This command sends a
.Dv SIGKILL
to the running name server and then
starts a new one.
.SH BUGS
.Sh BUGS
Does not check to see if the name server is actually running, and could
use a stale PID cache file which may result in the death of an unrelated
process.
.PP
.Pp
Does not wait after killing the old server before starting a new one; since
the server could take some time to die and the new one will experience a
fatal error if the old one isn't gone by the time it starts, you can be left
in a situation where you have no name server at all.
.SH SEE ALSO
@INDOT@named(@SYS_OPS_EXT@), @INDOT@named.reload(@SYS_OPS_EXT@)
.Sh SEE ALSO
.Xr @INDOT@named @SYS_OPS_EXT@ ,
.Xr @INDOT@named.reload @SYS_OPS_EXT@