This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/358] New: getaddrinfo hints.ai_socktype=0, service non-null not RFC3493 compliant
- From: "dlstevens at us dot ibm dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 30 Aug 2004 21:21:58 -0000
- Subject: [Bug libc/358] New: getaddrinfo hints.ai_socktype=0, service non-null not RFC3493 compliant
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
RFC 3493 section 6.1 (p.26) specifies:
"The ai_socktype field to which argument hints points specifies the
socket type for the service, as defined for socket(). If a specific
socket type is not given (for example, a value of zero) and the
service name could be interpreted as valid with multiple supported
socket types, the implementation shall attempt to resolve the service
name for all supported socket types and, in the absence of errors,
all possible results shall be returned."
When calling getaddrinfo with hints.ai_socktype=0 and service name "513", it
returns error "-8" ("servname not supported for ai_socktype"). It should instead
return a socktype SOCK_STREAM record (for "login") and a SOCK_DGRAM record
(for "who").
--
Summary: getaddrinfo hints.ai_socktype=0, service non-null not
RFC3493 compliant
Product: glibc
Version: 2.3.2
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: dlstevens at us dot ibm dot com
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=358
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.