All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Asmitha Karunanithi <asmithakarun@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Resolving service name conflicts
Date: Wed, 2 Sep 2020 10:58:01 -0500	[thread overview]
Message-ID: <20200902155801.GX3532@heinlein> (raw)
In-Reply-To: <CANGK-S5k=Dy+nf9cDPwNxcU_DELyaAkbmXjsotgpunQscaQ9Bw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-02 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  5:08 Resolving service name conflicts Asmitha Karunanithi
2020-09-02 15:58 ` Patrick Williams [this message]
2020-09-03  7:49   ` Asmitha Karunanithi
2020-09-03 12:37     ` Michael Richardson
2020-09-03 10:15 ` Jeremy Kerr
2020-09-04 16:37   ` Patrick Williams
2020-09-05  7:35     ` Asmitha Karunanithi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200902155801.GX3532@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=asmithakarun@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.