NAME<\/a> avahi.service \u2212 avahi-daemon static service file<\/p>\n \/etc\/avahi\/services\/*.service<\/b><\/p>\n \/etc\/avahi\/services\/*.service<\/i><\/b> are XML fragments containing static DNS-SD service data. Every service file can contain multiple service definitions which share the same name. This is useful for publishing service data for services which implement multiple protocols. (i.e. a printer implementing _ipp._tcp and _printer._tcp)<\/p>\n The Avahi Developers
SYNOPSIS<\/a>
DESCRIPTION<\/a>
XML TAGS<\/a>
AUTHORS<\/a>
SEE ALSO<\/a>
COMMENTS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
XML TAGS <\/a> <\/h2>\n
one
replace-wildcards<\/b> is “yes”, any occurence of the string “%h” will be
replaced by the local host name. This can be used for service names
like “Remote Terminal on %h”. If replace-wildcards<\/b> is not specified,
defaults to “no”.
exactly one service type. Should contain one
element. Optionally it may contain one
any number of
attribute protocol<\/b> specifies the protocol to advertise the service on.
If any<\/b> is used (which is the default), the service will be advertised
on both IPv4 and IPv6.
“_http._tcp”.
service. e.g. “_anon._sub._ftp._tcp”.
omited defaults to the default domain of the avahi daemon. (probably
.local)
should be a host that is resolvable by multicast or unicast DNS. Please
note that you need to specify a fully-qualified domain name (FQDN)
here, i.e. .local is not appended implicitly! The host name doesn\u2019t
need to be part of the domain specified in
avahi.hosts(5)<\/b> for more information how to publish additional host name
mappings.
record data. If value-format<\/b> is “text”, the value of the TXT record is
taken verbatim. If value-format<\/b> is “binary-hex” then the value of TXT
record is decoded by taking pairs of characters after the “=” char and
interpreting them as the textual representation of the two-digit
hexadecimal number. Both uppercase and lowercase hexadecimal digits are
allowed. The 0x or 0X prefix is not allowed. This requires the length
of the value to be even. If value-format<\/b> is “binary-base64” then the
value of TXT record is decoded with a base64 decoder. The character set
used is A-Za-z0-9+\/. This requires the length of the value to be a
multiple of 4, with “=” as padding at the end. If value-format<\/b> is not
specified, defaults to “text”. Examples (all the values are decoded to
the string “value” without quotes):<\/p>\nAUTHORS <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n