Date: Sun, 5 Oct 2008 23:29:46 GMT From: Nate Eldredge <neldredge@math.ucsd.edu> To: freebsd-gnats-submit@FreeBSD.org Subject: docs/127890: socket(2) man page should explain that protocol can be 0 Message-ID: <200810052329.m95NTkD4065133@www.freebsd.org> Resent-Message-ID: <200810052330.m95NU5In039428@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 127890 >Category: docs >Synopsis: socket(2) man page should explain that protocol can be 0 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 05 23:30:05 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Nate Eldredge >Release: 7.0-RELEASE-p4 >Organization: >Environment: FreeBSD vulcan.lan 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #13: Wed Sep 3 16:13:10 PDT 2008 nate@vulcan.lan:/usr/obj/usr/src/sys/VULCAN amd64 >Description: The man page for socket(2) should explain that the protocol argument can be set to 0 in the common situation where there is only one protocol for the given protocol family and type. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810052329.m95NTkD4065133>