From: Mike Brady <mikebrady@eircom.net>
To: cygwin@cygwin.com
Subject: Re: Question about D-Bus and cygrunsrv
Date: Thu, 21 Feb 2019 17:40:00 -0000 [thread overview]
Message-ID: <23766B16-3812-4D94-AA7C-C61C167A05C9@eircom.net> (raw)
In-Reply-To: <287EA5C9-AEDB-417D-8E1D-29405AB24325@eircom.net>
Hello again. Further to the rather vague email below, here is a link to what I did to install Shairport Sync on a fresh Cygwin installation:
https://github.com/mikebrady/shairport-sync/blob/development/CYGWIN.md <https://github.com/mikebrady/shairport-sync/blob/development/CYGWIN.md>
Regards
Mike
> On 20 Feb 2019, at 21:50, Mike Brady <mikebrady@eircom.net> wrote:
>
> Hi there. I'm trying to set up Shairport Sync as a CYGWIN service, and I'm trying to use cygrunsrv.
>
> Briefly, I can get everything to work properly except the D-Bus interface -- when shairport-sync is installed as a service, it can't "own" a well-known name on the "system" D-Bus.
>
> I built a configuration and installer for shairport sync essentially by copying the avahi-daemon-config file.
>
> The Avahi deamon uses the system D-Bus successfully under the username "SYSTEM" and without (AFAICS) changing IDs. But for the life of me, I can't get Shairport Sync to work the same way.
>
> Incidentally, if I change the D Bus policy file for Shairport Sync to be allowed to own its well-known name on D Bus when running under the logged in account, everything is peachy.
>
> Any suggestions gratefully received. Incidentally, I'm the main developer of Shairport Sync -- https://github.com/mikebrady/shairport-sync.
>
> Best wishes
> Mike Brady
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-02-21 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 22:01 Mike Brady
2019-02-21 17:40 ` Mike Brady [this message]
2019-02-22 10:21 ` Corinna Vinschen
2019-02-22 15:14 ` Mike Brady
2019-02-23 0:00 ` René Berber
2019-02-26 8:41 ` L A Walsh
2019-02-27 12:37 ` Mike Brady
2019-10-22 14:07 ` Mike Brady
2019-10-22 14:33 ` Mike Brady
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=23766B16-3812-4D94-AA7C-C61C167A05C9@eircom.net \
--to=mikebrady@eircom.net \
--cc=cygwin@cygwin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).