1slpd.reg(4) File Formats slpd.reg(4)
2
3
4
6 slpd.reg - serialized registration file for the service location proto‐
7 col daemon (slpd)
8
10 /etc/inet/slpd.reg
11
12
14 The serialized registration file contains a group of registrations that
15 slpd(1M) registers when it starts. These registrations are primarily
16 for older service programs that do not internally support SLP and can‐
17 not be converted. The character format of the registration file is
18 required to be ASCII. To use serialized registrations, set the
19 net.slp.serializedRegURL property in slp.conf(4) to point at a valid
20 slpd.reg file. The syntax of the serialized registration file, in ABNF
21 format (see RFC 2234), is as follows:
22
23 ser-file = reg-list
24 reg-list = reg / reg reg-list
25 reg = creg / ser-reg
26 creg = comment-line ser-reg
27 comment-line = ( "#" / ";" ) 1*allchar newline
28 ser-reg = url-props [slist] [attr-list] newline
29 url-props = surl "," lang "," ltime [ "," type ] newline
30 surl = ;The registration's URL. See
31 ; [8] for syntax.
32 lang = 1*8ALPHA [ "-" 1*8ALPHA ]
33 ;RFC 1766 Language Tag see [6].
34 ltime = 1*5DIGIT
35 ; A positive 16-bit integer
36 ; giving the lifetime
37 ; of the registration.
38 type = ; The service type name, see [7]
39 ; and [8] for syntax.
40 slist = "scopes" "=" scope-list newline
41 scope-list = scope-name / scope-name "," scope-list
42 scope = ; See grammar of [7] for
43 ; scope-name syntax.
44 attr-list = attr-def / attr-def attr-list
45 attr-def = ( attr / keyword ) newline
46 keyword = attr-id
47 attr = attr-id "=" attr-val-list
48 attr-id = ;Attribute id, see [7] for syntax.
49 attr-val-list = attr-val / attr-val "," attr-val-list
50 attr-val = ;Attribute value, see [7] for syntax
51 allchar = char / WSP
52 char = DIGIT / ALPHA / other
53 other = %x21-%x2f / %x3a-%x40 /
54 %x5b-%x60 / %7b-%7e
55 ; All printable, nonwhitespace US-ASCII
56 ; characters.
57 newline = CR / ( CRLF )
58
59
60
61 The syntax for attributes and attribute values requires that you use a
62 backslash to escape special characters, in addition to non-ASCII char‐
63 acters, as specified in RFC 2608. The slpd command handles serialized
64 registrations exactly as if they were registered by an SA. In the url-
65 props production, the type token is optional. If the type token is
66 present for a service: URL, a warning is signalled, and the type name
67 is ignored. If the maximum lifetime of 65535 seconds is specified, the
68 registration is taken to be permanent, and it is continually refreshed
69 by the DA or SA server until it exits.
70
71
72 Scopes can be included in a registration by including an attribute def‐
73 inition with tag scopes followed by a comma-separated list of scope
74 names immediately after the url-props production. If the optional
75 scope-list is present, the registations are made in the indicated
76 scopes; otherwise, they are registered in the scopes with which the DA
77 or SA server was configured through the net.slp.useScopes property. If
78 any conflicts occur between the scope list and the net.slp.useScopes
79 property, an error message is issued by way of syslog(3C). Refer to
80 information regarding LOG_INFO in syslog(3C).
81
82
83 Service advertisements are separated by a single blank line. Addition‐
84 ally, the file must end with a single blank line.
85
87 Example 1 Using a Serialized Registration File
88
89
90 The following serialized registration file shows an instance of the
91 service type foo, with a lifetime of 65535 seconds, in the en locale,
92 with scope somescope:
93
94
95 # register foo
96 service:foo://fooserver/foopath,en,65535
97 scopes=somescope
98 description=bogus
99 security=kerberos_v5
100 location=headquarters
101
102 # next registration...
103
104
106 See attributes(5) for descriptions of the following attributes:
107
108
109
110
111 ┌─────────────────────────────┬─────────────────────────────┐
112 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
113 ├─────────────────────────────┼─────────────────────────────┤
114 │Availability │SUNWslpr │
115 ├─────────────────────────────┼─────────────────────────────┤
116 │CSI │Enabled │
117 ├─────────────────────────────┼─────────────────────────────┤
118 │Interface Stability │ Standard │
119 └─────────────────────────────┴─────────────────────────────┘
120
122 slpd(1M), slp_api(3SLP), syslog(3C), slp.conf(4), attributes(5)
123
124
125 Crocker, D. and Overell, P., RFC 2234, Augmented BNF for Syntax Speci‐
126 fications: ABNF, The Internet Society, November 1997.
127
128
129 Guttman, E., Perkins, C., Veizades, J., and Day, M., RFC 2608, Service
130 Location Protocol, Version 2, The Internet Society, June 1999.
131
132
133 Kempf, J. and Guttman, E., RFC 2614, An API for Service Location, The
134 Internet Society, June 1999.
135
136
137
138SunOS 5.11 17 Nov 1999 slpd.reg(4)