Resolving service name conflicts

[Asmitha Karunanithi]

Hi Patrick,

Yup, it would be like "ssh-hostname" because there would be service name
conflicts, say if there are 100 systems in the network publishing the
service with the same name, there would be name conflicts for 100 times and
finally, the service would be published as "ssh#101" to the network.

To avoid this, if we append the service name with the hostname which will
be unique, we make sure that the service name would also be unique thus
resolving the service name conflicts.

Example would be:

    <name>ssh-(hostname)</name>
    <service>
        ....
    </service>

Else, one other solution would be to push a patch for avahi, to stop
looking for service name conflicts (unique service name).
Your thoughts on the same, Patrick?

On Wed, Sep 2, 2020 at 9:28 PM Patrick Williams <patrick at stwcx.xyz> wrote:

> 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
>


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