[Home]

Issue of the Standard # S0363

Brief

Lack of details in requirements to getprotobyname(), getprotobynumber(), getservbyname() and getservbyport() functions.

Detailed Description

The description of getprotobyname() and getprotobynumber() functions has no requirements for the changes of pointer to the next entry in the network protocol database after the functions’ call. Possible behavior is to set the next entry to the first entry, to set the next entry to the next of found entry, or to leave the next entry unchanged. The behavior of the functions affects the sequential calls of the getprotoent() function.
The same is for getservbyname() and getservbyport() functions that search the network services database and affect the sequential calls of the getservent() function.

Problem location(s) in the standard

The Open Group Base Specifications Issue 6 IEEE Std 1003.1, 2004 Edition (SUS 3.0), System Interfaces, the description of <nobr>getprotobyname()</nobr>, <nobr>getprotobynumber()</nobr>, <nobr>getservbyname()</nobr> and <nobr>getservbyport()</nobr> functions.

[Home]