[src/netbsd-1-5]: src/share/man/man4 Pull up revision 1.13 (requested by wiz):

[he <he%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/ba50feb1e5d5
branches:  netbsd-1-5
changeset: 491413:ba50feb1e5d5
user:      he <he%NetBSD.org@localhost>
date:      Thu Apr 26 09:28:56 2001 +0000

description:
Pull up revision 1.13 (requested by wiz):
  Correct setsockopt(2) reference.

diffstat:

 share/man/man4/ipsec.4 |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (27 lines):

diff -r 2ce7e4347bdc -r ba50feb1e5d5 share/man/man4/ipsec.4
--- a/share/man/man4/ipsec.4    Thu Apr 26 09:27:25 2001 +0000
+++ b/share/man/man4/ipsec.4    Thu Apr 26 09:28:56 2001 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: ipsec.4,v 1.10.2.1 2000/10/26 21:09:17 tv Exp $
+.\"    $NetBSD: ipsec.4,v 1.10.2.2 2001/04/26 09:28:56 he Exp $
 .\"    $KAME: ipsec.4,v 1.12 2000/06/14 13:05:29 itojun Exp $
 .\"
 .\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
@@ -104,7 +104,7 @@
 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 @@
 .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.