Resolving service name conflicts

Asmitha Karunanithi asmithakarun at gmail.com
Wed Sep 2 15:08:55 AEST 2020


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>


I just wanted to clarify if the above idea would be the right solution to
resolve the service name conflict or is there any other way that is
currently available to resolve this issue?

-- 
Thanks & Regards,
Asmitha Karunanithi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200902/dbd8faf4/attachment-0001.htm>


More information about the openbmc mailing list