services(5) [ultrix man page]

services(5)							File Formats Manual						       services(5)

Name
       services - service name file

Description
       The file is an ASCII file that contains information regarding the known services available in the DARPA Internet.  For each service, a sin-
       gle line should be present with the following information:

       official service name
       port number
       protocol name
       aliases

       Each name is separated from the next by a new line.  Items are separated by any number of blanks or tab characters or both.  The port  num-
       ber  and  protocol  name are considered a single item; a backslash () is used to separate the port and protocol (for example, 512/tcp).  A
       number sign (#) indicates the beginning of a comment; characters up to the end of the line are not interpreted by routines that search  the
       file.

       Service names can contain any printable character other than a field delimiter, newline, or comment character.

       The  database  may be distributed in a network by a naming service, such as Yellow Pages or BIND/Hesiod.  See the Guide to the Yellow Pages
       Service or the chapter on Hesiod in the Guide to the BIND/Hesiod Service for setup information.

Files
See Also
       getservent(3n)
       Guide to the BIND/Hesiod Service
       Guide to the Yellow Pages Service

																       services(5)

getservent(3n)															    getservent(3n)

Name
       getservent, getservbyname, getservbyport, setservent, endservent - get services entry

Syntax
       #include <netdb.h>

       struct servent *getservent()

       struct servent *getservbyname(name, proto)
       char *name, *proto;

       struct servent *getservbyport(port, proto)
       int port; char *proto;

       void setservent(stayopen)
       int stayopen

       void endservent()

Description
       The  and subroutines each return a pointer to an object with the following structure containing the broken-out fields of a line in the net-
       work database.
       struct	 servent {
	    char *s_name;	 /* official name of service */
	    char **s_aliases;	 /* alias list */
	    long s_port;	 /* port service resides at */
	    char *s_proto;	 /* protocol to use */
       };

       The members of this structure are:

       s_name	  The official name of the service.

       s_aliases  A zero terminated list of alternate names for the service.

       s_port	  The port number at which the service resides.  Port numbers are returned in network byte order.

       s_proto	  The name of the protocol to use when contacting the service.

       If the stayopen flag on a subroutine is NULL, the database is opened.  Otherwise, the has the effect of rewinding the database.	 The  sub-
       routine may be called to close the database when processing is complete.

       The  subroutine reads the next line; and search until a matching name or port is found (or until EOF is encountered).  The subroutine keeps
       a pointer in the database, allowing successive calls to be used to search the entire file.  If a non-NULL protocol name, is also  supplied,
       searches must also match the protocol.

       The  routine  must  be  called  before a loop that uses in order to initialize variables in the routine and an must be used after the loop.
       Both and make calls to and

Restrictions
       All information is contained in a static area so it must be copied if it is to be saved.

       If the Yellow Pages Service is running, does not return the entries in any particular order.  See the Guide to the Yellow Pages Service for
       setup information.

       The database can also be distributed by the BIND/Hesiod naming service.	See the Guide to the BIND/Hesiod Service for more information.

Return Values
       Null pointer(0) returned on EOF or error.

Files
See Also
       services(5), svc.conf(5)
       Guide to the BIND/Hesiod Service
       Guide to the Yellow Pages Service

																    getservent(3n)