Resolving service name conflicts

[Patrick Williams]

On Wed, Sep 02, 2020 at 10:38:55AM +0530, Asmitha Karunanithi wrote:
> Hi All,
> 
> Hope all are doing good.
> 
> When I was trying to do 'avahi-browse', I was able to see service name
> conflicts (since the service with the same name would be published by
> various clients in the network and I could see <servicename>#100, after
> trying for 99 times).
> 
> To resolve this, the idea is to append the hostname of the client with the
> service name (whenever the service is being published), given that the
> hostname will always be unique in my case.
> 
> So, the service file would look like: (example.service)
> 
> <service-group>
> 
>        <name>example-hostname</name>
> 
>        <service>
> 
>                <type>...</type>
> 
>                <port>...</port>
> 
>        </service>
> 
> </service-group>

Can you give an example of what a service name would be in this context?
Is it like 'ssh'?  I don't think you should be advertising services as
'ssh-hostname' in that case.

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200902/a66c38ad/attachment.sig>