tail head cat sleep
QR code linking to this page

Manual Pages  — SERVICES

NAME

services – service name data base

CONTENTS

DESCRIPTION

The services file contains information regarding the known services available in the 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 (e.g. ``512/tcp''). A ``#'' indicates the beginning of a comment; subsequent characters up to the end of the line are not interpreted by the routines which search the file.

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

If "db" is specified as source in the nsswitch.conf(5), /var/db/services.db is searched. The database in /var/db/services.db needs to be updated with services_mkdb(8) after changes to the services file have been applied.

NIS INTERACTION

Access to the NIS services.byname map can be enabled by adding a single ``+'' on a line by itself in the /etc/services file. This causes the contents of the NIS services map to be inserted at the location where the ``+'' appears.

FILES

/etc/services
  The services file resides in /etc.

SEE ALSO

getservent(3), nsswitch.conf(5), services_mkdb(8)

HISTORY

The services file format appeared in BSD 4.2 .

BUGS

A name server should be used instead of a static file.

SERVICES (5) April 4, 2010

tail head cat sleep
QR code linking to this page


Please direct any comments about this manual page service to Ben Bullock.

I have a natural revulsion to any operating system that shows so little planning as to have to named all of its commands after digestive noises (awk, grep, fsck, nroff).