
550 Chapter 16
Each SLP log entry includes a code that indicates the type of event that has occurred.
Using the Attributes List
Services may advertise their presence on the network along with a list of attributes. These
attributes are listed as a string encoding that follows a specific format. Directory agents use
the attributes list to help match client requests with appropriate services.
Here is an example of an attributes list for a network printer named Amazon. It’s an LPR
printer located in the Research scope. The attributes list entered by the administrator might
look like this:
(Name=Amazon),(Description=For research dept only),(Protocol=LPR),(location-
description=bldg 6),(media-size=na-letter),(resolution=res-600),x-OK
The directory agent must scan any included attributes lists when it’s looking for services. So,
if you create an attributes list that is incorrectly formatted, you could inadvertently block the
directory agent from using a service.
Where to Find More Information
Request for Comments (RFC) documents provide an overview of a protocol or service and
details about how the protocol should behave. If you are a novice server administrator, you’ll
probably find some of the background information in an RFC helpful. If you are an
experienced server administrator, you can find all the technical details about a protocol in its
RFC document. You can search for RFC documents by number at this Web site:
www.faqs.org/rfcs
m For SLP DA, see RFC 2608.
Code Event type
REG Service registrations and deregistrations
EXP Service deregistrations only
SR Service requests
DA Directory agent information requests
ERR SLP errors
Kommentare zu diesen Handbüchern