SERVICES(5) — System Interface Manual — File Formats
NAME
services − service name data base
SYNOPSIS
/usr/lib/services
DESCRIPTION
The services file contains information regarding the known services available in the DARPA Internet. For each service a single line should be present with the following information:
official service name
port number
protocol name
aliases
Items are separated by any number of blanks and/or tab characters. The port number and protocol name are considered a single item; a “/” is used to separate the port and protocol (for instance, “512/tcp”). A “#” indicates the beginning of a comment; characters up to the end of the line are not interpreted by routines which search the file.
Service names may contain any printable character other than a field delimiter, newline, or comment character.
EXAMPLE
Here is an example of the /usr/lib/services file from the Sun UNIX System.
#
# Network services, Internet style
#
echo7/udp
discard9/udpsink null
systat11/tcp
daytime13/tcp
netstat15/tcp
ftp21/tcp
telnet23/tcp
smtp25/tcpmail
time37/tcptimserver
name42/tcpnameserver
whois43/tcp
mtp57/tcp# deprecated
#
# Host specific functions
#
tftp69/udp
rje77/tcp
finger79/tcp
link87/tcpttylink
supdup95/tcp
#
# UNIX specific services
#
exec512/tcp
login513/tcp
shell514/tcpcmd
efs520/tcp
biff512/udpcomsat
who513/udpwhod
syslog514/udp
talk517/udp
route520/udprouter routed # 521 also
FILES
/usr/lib/services
SEE ALSO
BUGS
A name server should be used instead of a static file. A binary indexed file format should be available for fast access.
Sun System Release 0.3 — 31 March 1983