Bug#233946: libc6-dev: <sys/un.h> does not define UNIX_PATH_MAX
On Tue, Feb 24, 2004 at 06:55:59PM +0100, Julien BLACHE wrote:
> > I don't know this is intentional or not, but there is no rule that we
> > need to define UNIX_PATH_MAX. In addition POSIX does not define its
> > path size (typically it's between 92 and 108, and linux is 108). If
> > you want to look UNIX_PATH_MAX like unix(7), see
> > /usr/include/linux/un.h .
>
> I haven't looked at other unices, but if the define is mentionned in
> the manpage, I guess it's for a reason. Portability comes to mind :)
The define is shown in *example* code. It doesn't say anywhere that it
must be defined.
> > I would like to close, OK?
>
> Either one of libc or the manpage needs to be fixed, I'll let you
> decide which one needs fixing.
The man page says "sun_path contains the zero-terminated pathname
of the socket in the file system.", which does not indicates any
length.
I agree with gotom, this is not a bug, the manpage does not state that
UNIX_MAX_PATH is set by any header, and it is merely shown in example
code.
We are open to suggestions and changes in the text of the manpage, what
would you like to see that might clarify this?
c.
Reply to: