Datasheet

“main” (Installation and Administration) 2004/6/25 13:29 page 456 #482
i
i
i
i
i
i
i
i
Static Registration via /etc/slp.reg.d/
Create a separate registration file for each new service. The following
is an example of a file for registering a scanner service:
## Register a saned service on this system
## en means english language
## 65535 disables the timeout, so the service registration does
## not need refreshes
service:scanner.sane://$HOSTNAME:6566,en,65535
watch-port-tcp=6566
description=SANE scanner daemon
The most important line in this file is the service URL, which begins
with service:. This contains the service type (scanner.sane)
and the address under which the service is available on the server.
h$HOSTNAMEi is automatically replaced with the full host name.
The name of the TCP port on which the relevant service can be found
follows, separated by a colon. Then enter the language in which the
service should appear and the duration of registration in seconds.
These should be separated from the service URL by commas. Set the
value for the duration of registration between 0 and 65535. 0 pre-
vents registration. 65535 removes all restrictions.
The registration file also contains the two variables
watch-tcp-port and description. The former links the SLP ser-
vice announcement to whether the relevant service is active because
slpd checks the status of the service. The second variable contains a
more precise description of the service that is displayed in suitable
browsers.
Note
YaST and SLP
Some services brokered by YaST, such as an installation
server or YOU server, perform this registration for you au-
tomatically when you activate SLP in the module dialogs.
YaST then creates registration files for these services.
Note
Static Registration with /etc/slp.reg
The only difference from the procedure described above is the group-
ing of all services within a central file.
456 21.6. SLP Services in the Network