search for: susv4

...t; > > Right. Today it only has an effect if the first argument to getaddrinfo > > > is NULL. The intension (IIUC) is that it should be used when you plan to > > > feed the result to bind (opposed to connect). > > > > What do you mean by "Today"? Both SuSv4 and the Linux man page are > > unequivocal about the _only_ use of that flag being to special case > > a NULL address (meaning 'this machine') to return either the wildcard > > address or the LOOPBACK address. > > I had in mind that at some point in the future (say...

...irst place. > > > > Right. Today it only has an effect if the first argument to getaddrinfo > > is NULL. The intension (IIUC) is that it should be used when you plan to > > feed the result to bind (opposed to connect). > > What do you mean by "Today"? Both SuSv4 and the Linux man page are > unequivocal about the _only_ use of that flag being to special case > a NULL address (meaning 'this machine') to return either the wildcard > address or the LOOPBACK address. I had in mind that at some point in the future (say with ipv8 or 802.11t-2042...

...actually be executed in the first place. > > Right. Today it only has an effect if the first argument to getaddrinfo > is NULL. The intension (IIUC) is that it should be used when you plan to > feed the result to bind (opposed to connect). What do you mean by "Today"? Both SuSv4 and the Linux man page are unequivocal about the _only_ use of that flag being to special case a NULL address (meaning 'this machine') to return either the wildcard address or the LOOPBACK address. That you'd use the wildcard address to bind a service to all addresses of 'this mach...

Hello Ron, On Thu, Feb 02, 2017 at 04:08:49PM +1030, Ron via Syslinux wrote: > On Sun, Jan 29, 2017 at 12:09:43PM +0100, Uwe Kleine-K?nig wrote: > > AI_CANONNAME is only relevant when the resulting official name is used, > > which is not the case in tftpd for the address to bind to. Also > > AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to > >