All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Lohr <Christophe.Lohr-+sCGM1tQGJejRLBOWInFB+yrfmlZI2zM@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Bug about UNIX_PATH_MAX in the manpage of Unix(7)
Date: Wed, 03 Nov 2010 15:38:10 +0100	[thread overview]
Message-ID: <4CD173D2.8020003@telecom-bretagne.eu> (raw)

File: /usr/share/man/man7/unix.7.gz
Version: 3.25-1
System: debian testing


Hi,
   Manpage of Unix(7) says:

---------------------------------
|    SYNOPSIS
|           #include <sys/socket.h>
|           #include <sys/un.h>
(../..)
|    DESCRIPTION
(../..)
|
|       Address Format
|           A Unix domain socket address is represented in the following 
structure:
|
|               #define UNIX_PATH_MAX    108
|
|               struct sockaddr_un {
|                   sa_family_t sun_family;               /* AF_UNIX */
|                   char        sun_path[UNIX_PATH_MAX];  /* pathname */
|               };
---------------------------------


However, UNIX_PATH_MAX is not defined in the mentioned include <sys/un.h>.
In fact, these definitions come from <linux/un.h>.

There is a confusion between the two includes (sys/un.h and linux/un.h).

Maybe they should be merged, but today it is not the case... :-(

Regards,
Christophe

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2010-11-03 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 14:38 Christophe Lohr [this message]
     [not found] ` <4CD173D2.8020003-+sCGM1tQGJejRLBOWInFB+yrfmlZI2zM@public.gmane.org>
2015-05-06  8:24   ` Bug about UNIX_PATH_MAX in the manpage of Unix(7) Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CD173D2.8020003@telecom-bretagne.eu \
    --to=christophe.lohr-+scgm1tqgjejrlbowinfb+yrfmlzi2zm@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.