Contents
Abstract
The service location protocol (SLP) was developed to simplify the configuration of networked clients within a local network. To configure a network client, including all required services, the administrator traditionally needs detailed knowledge of the servers available in the network. SLP makes the availability of selected services known to all clients in the local network. Applications that support SLP can use the information distributed and be configured automatically.
SUSE Linux EnterpriseŽ supports installation using installation sources provided with SLP and contains many system services with integrated support for SLP. YaST and Konqueror both have appropriate front-ends for SLP. You can use SLP to provide networked clients with central functions, such as an installation server, file server, or print server on your system.
![]() | SLP Support in SUSE Linux Enterprise |
|---|---|
Services that offer SLP support include cupsd, rsyncd, ypserv, openldap2, openwbem (CIM), ksysguardd, saned, kdm vnc login, smpppd, rpasswd, postfix, and sshd (via fish). | |
slpd must run on your system to offer services with SLP. It is not necessary
to start this daemon simply to make service inquiries.
Like most system services in SUSE Linux Enterprise, the
slpd daemon is controlled by means of a
separate initialization script.
The daemon is inactive by default. To activate it for
the duration of a session, run
rcslpd start as
root to start it and
rcslpd stop to stop
it. Perform a restart or status check with
restart or status. If
slpd should be active by default, enable slpd in
YaST +
or run the insserv slpd command
once as root. This
automatically includes slpd in the set
of services to start when the system boots.