From owner-freebsd-current  Thu Mar 20 05:45:27 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA14686
          for current-outgoing; Thu, 20 Mar 1997 05:45:27 -0800 (PST)
Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14680
          for <freebsd-current@freebsd.org>; Thu, 20 Mar 1997 05:45:23 -0800 (PST)
Received: from localhost (taob@localhost)
          by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP
	  id IAA08831; Thu, 20 Mar 1997 08:44:41 -0500 (EST)
Date: Thu, 20 Mar 1997 08:44:41 -0500 (EST)
From: Brian Tao <taob@nbc.netcom.ca>
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: getpeername xrefs?
In-Reply-To: <19970312011918.39824@hydrogen.nike.efn.org>
Message-ID: <Pine.GSO.3.95.970320084356.8798C-100000@tor-adm1.nbc.netcom.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 12 Mar 1997, John-Mark Gurney wrote:
>
> is there any good reason why getpeername doesn't have xrefs in
> related man pages?  (like socket(2), getsockname(2), etc...)?

    I think that would be a good idea... I was going through the man
pages for socket, listen, bind, accept, etc. looking for getpeername
(though I didn't know it at the time ;-)).
-- 
Brian Tao (BT300, taob@netcom.ca)
"Though this be madness, yet there is method in't"