Datasheet
“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 455 — #481
i
i
i
i
i
i
i
i
21
Linux in the Network
21.6 SLP Services in the Network
The service location protocol (SLP) was developed with the aim of simplify-
ing the configuration of networked clients within a local network. To con-
figure a network client, including all required services, the administrator
traditionally needs detailed knowledge of the servers available in the net-
work. SLP is used to make the availability of a certain service known to all
clients in the local network. Applications that support SLP can use the in-
formation distributed and be configured automatically.
Note
SLP Support in SUSE LINUX Enterprise Server
Services that offer SLP support include cupsd, rsyncd, ypserv,
openldap2, openwbem (CIM), ksysguardd, saned, kdm vnc
login, smpppd, rpasswd, postfix, and sshd (via fish.)
Note
21.6.1 SLP Support in SUSE LINUX
SUSE LINUX supports installation using installation sources provided via
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 instal-
lation server, YOU server, file server, or print server on your SUSE LINUX
Enterprise Server.
Installation via SLP
If you offer an installation server with SUSE LINUX installation media
within your network, this can be registered with SLP. For details, see Sec-
tion 4.1 on page 152. If SLP installation is selected, linuxrc starts an SLP
inquiry after the system has booted from the selected boot medium and
displays the sources found.
Registering Your Own Services
Many applications under SUSE LINUX already have integrated SLP sup-
port through the use of the libslp library. If a service has not been com-
piled with SLP support, use one of the following methods to make it avail-
able with SLP:
455SUSE LINUX Enterprise Server










