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

Correct cross-references:

Browse Source 
setsockopt.3 --> setsockopt.2
  syslog.8 --> syslogd.8
  tcpdump.8 --> tcpdump.1

MFC after:	1 week
This commit is contained in:
Maxim Sobolev 2001-06-05 12:50:33 +00:00
parent fe11f6f605
commit 1cdc139280
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=77761
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
share/man/man4/ipsec.4
View File

@ -104,7 +104,7 @@ by using the above described APIs.
The kernel implements experimental policy management code.
You can manage the IPsec policy in two ways.
One is to configure per-socket policy using
.Xr setsockopt 3 .
.Xr setsockopt 2 .
The other is to configure kernel packet filter-based policy using
.Dv PF_KEY
interface, via
@ -113,7 +113,7 @@ In both cases, IPsec policy must be specified with syntax described in
.Xr ipsec_set_policy 3 .
.Pp
With
.Xr setsockopt 3 ,
.Xr setsockopt 2 ,
you can define IPsec policy in per-socket basis.
You can enforce particular IPsec policy onto packets that go through
particular socket.

2
share/man/man4/ng_bpf.4
View File

@ -135,7 +135,7 @@ This node shuts down upon receipt of a
control message, or when all hooks have been disconnected.
.Sh EXAMPLES
It is possible to configure a node from the command line, using
.Xr tcpdump 8
.Xr tcpdump 1
to generate raw BPF instructions which are then fed into an
.Xr awk 1
script to create the ASCII form of a

2
usr.sbin/lpr/lpr/printcap.5
View File

@ -374,7 +374,7 @@ are sent to the corresponding
.Cm lf
file.
The filters may, of course, use
.Xr syslog 8
.Xr syslogd 8
themselves.
.Pp
Error messages sent to the console have a carriage return and a line