bind.2, connect.2, getpeername.2, getsockname.2, getsockopt.2: Replace discussion of 'socklen_t' with reference to accept(2)

The discussion of 'socklen_t' editorializes and is repeated
across several pages. Replace it with a reference to accept(2),
where some details about this type are provided.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/bind.2

@@ -248,15 +248,9 @@ and this header file is not required on Linux.
 However, some historical (BSD) implementations required this header
 file, and portable applications are probably wise to include it.
 
-The third argument of
-.BR bind ()
-is in reality an
-.I int
-(and this is what 4.x BSD and libc4 and libc5 have).
-Some POSIX confusion resulted in the present
-.IR socklen_t ,
-also used by glibc.
-See also
+For background on the
+.I socklen_t
+type, see
 .BR accept (2).
 .SH BUGS
 The transparent proxy options are not described.

man2/connect.2

@@ -260,15 +260,9 @@ and this header file is not required on Linux.
 However, some historical (BSD) implementations required this header
 file, and portable applications are probably wise to include it.
 
-The third argument of
-.BR connect ()
-is in reality an
-.I int
-(and this is what 4.x BSD and libc4 and libc5 have).
-Some POSIX confusion resulted in the present
-.IR socklen_t ,
-also used by glibc.
-See also
+For background on the
+.I socklen_t
+type, see
 .BR accept (2).
 
 If

man2/getpeername.2

@@ -103,15 +103,9 @@ POSIX.1-2001, POSIX.1-2008, SVr4, 4.4BSD
 .RB ( getpeername ()
 first appeared in 4.2BSD).
 .SH NOTES
-The third argument of
-.BR getpeername ()
-is in reality an
-.I "int\ *"
-(and this is what 4.x BSD and libc4 and libc5 have).
-Some POSIX confusion resulted in the present
-.IR socklen_t ,
-also used by glibc.
-See also
+For background on the
+.I socklen_t
+type, see
 .BR accept (2).
 
 For stream sockets, once a

man2/getsockname.2

@@ -101,15 +101,9 @@ first appeared in 4.2BSD).
 .\" SVr4 documents additional ENOMEM
 .\" and ENOSR error codes.
 .SH NOTES
-The third argument of
-.BR getsockname ()
-is in reality an
-.I "int\ *"
-(and this is what 4.x BSD and libc4 and libc5 have).
-Some POSIX confusion resulted in the present
-.IR socklen_t ,
-also used by glibc.
-See also
+For background on the
+.I socklen_t
+type, see
 .BR accept (2).
 .SH SEE ALSO
 .BR bind (2),

man2/getsockopt.2

@@ -186,19 +186,9 @@ and this header file is not required on Linux.
 However, some historical (BSD) implementations required this header
 file, and portable applications are probably wise to include it.
 
-The
-.I optlen
-argument of
-.BR getsockopt ()
-and
-.BR setsockopt ()
-is in reality an
-.I "int [*]"
-(and this is what 4.x BSD and libc4 and libc5 have).
-Some POSIX confusion resulted in the present
-.IR socklen_t ,
-also used by glibc.
-See also
+For background on the
+.I socklen_t
+type, see
 .BR accept (2).
 .SH BUGS
 Several of the socket options should be handled at lower levels of the