X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=YASh3naXqUSd6/EBRUMMmaPkMuYxFxaovBx2UVuFDsRSshllyRG2a
	S3ta9HlPTex89jf3+hV21uzCCbSiJrF0IGJ88rrgia9q79/NVNPEHFrMkNZeUSMq
	mr47pFH+hmYZVc3t16qZX2QGxCPnyezVXfasgMC6ApzHSGd6kKjC8A=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=5kKlTLRKfTisezs1iHN9CiNkEEs=; b=vDArXxbBcD5q4Jrpfnfbp2brUO44
	VADP6zWa8B+H7R0hxQvAHjl3YTbRUl0gE8l5mh+AGr1vL0u3hIGRTKp10rrTcaIB
	1Gf1djFX1tzzAjrOnxkOzqAr8RdqnY5gZU5ory0Kw1KW9eNjFmpPTQK8Zu8o65+M
	t8FPB/2EGWmC80M=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Tue, 28 Oct 2014 16:16:09 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.1
Message-ID:	<20141028151609.GN20607@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<announce DOT 20141022092323 DOT GH32374 AT calimero DOT vinschen DOT de> <C9D37D92E903B347A31B9CF82643BA28072F9229 AT 046-CH1MPN1-043 DOT 046d DOT mgd DOT msft DOT net> <20141022135424 DOT GB18857 AT calimero DOT vinschen DOT de> <C9D37D92E903B347A31B9CF82643BA28072FFFD5 AT 046-CH1MPN1-043 DOT 046d DOT mgd DOT msft DOT net> <20141027212637 DOT GZ20607 AT calimero DOT vinschen DOT de> <C9D37D92E903B347A31B9CF82643BA2807300C63 AT 046-CH1MPN1-043 DOT 046d DOT mgd DOT msft DOT net> <20141028142021 DOT GL20607 AT calimero DOT vinschen DOT de> <544FAF26 DOT 3040102 AT redhat DOT com>
MIME-Version:	1.0
In-Reply-To:	<544FAF26.3040102@redhat.com>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--Yvzb+MHGXtbPBi5F
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Oct 28 08:58, Eric Blake wrote:
> On 10/28/2014 08:20 AM, Corinna Vinschen wrote:
> >>> Now that you mention it... yes, a service dependency might be helpful.
> >>> Unfortunately it's tricky to automate this.  Is it possible to add
> >>> service deps after having installed a service?
> >>
> >> According to
> >> http://serverfault.com/questions/24821/how-to-add-dependency-on-a-wind=
ows-service-after-the-service-is-installed
> >> it is possible to add a dependency to an already existing service.  I
> >> agree it would be hard to automate in the install scripts, as one
> >> would have to either ask the user about their intent to run other
> >> services or rely that they configured cygserver first and then check
> >> to see if it has been already configured to determine if a dependency
> >> should be created.  I would think that some instructions in the docs
> >> near the statement mentioned above would be more than sufficient,
> >> since this is a "fine tuning" sort of thing.
> >=20
> > Agreed.  Do you have some idea how to phrase this?  I'd be grateful
> > for a nice two or three paragraphs discussing this.
>=20
> On Linux, systemd has a notion of soft dependencies, where any service
> can do a one-sided advertisement that "if this other service is also
> installed, then here is the order that must be observed between bringing
> the two services up; but there is no requirement that the other service
> be installed".  Note in particular that both 'before' and 'after' soft
> dependencies can be specified.  I wonder if cygserver could be taught to
> do something similar - but it would probably be a lot of work.

There's a twist here.  The activity, whether or not to ask cygserver, is
not controlled by cygserver.  The decision is made in the first process
of a Cygwin process tree, and then if any other process fails to contact
cygserver,

One idea to workaround would be to check for Session 0, the session
in which the service processes run.  If a process fails to contact
cygserver, it checks if it's running in session 0.  If so, it will
try to contact cygserver again later.

Potential downside: This might slowdown account handling again, but
AFAIK, trying to open a non-existing named pipe (used to communicate
between process and cygserver) is blazingly fast.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--Yvzb+MHGXtbPBi5F
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUT7M5AAoJEPU2Bp2uRE+gCiwP/i2h1iThzIEZBpL5+k7ekzpl
UivMxfD0QxLijTHUaJ6cysHjbln+NtzpdZr1Aru2ykKJYHnDqyyJPc9wJ5wmO0LX
rgdjIyUy5MGkYDQngVrTx/ea3714YzYZSzj4sHAzRDwuz2ZgwVaKA6O0D08NOzYp
sh6th4TwvmbRsquAvLdqPxVXjKZ8sz9WneDKFgBM4qbGa8Lok/ow0s2O/vJgVKJz
eCxdUXx99RgjRWO3st/5s1T2PDgXBo7yLliQHl+SDI1pvlpNomkMK7MeOL8RD3xQ
ulxzz8/M4b09h6o2tEhZxFXhB9bn5fIW/azzFaTlq+lYseHXZF4tr9nUmWLipo9t
80ZLNsUw1RLanc5qr+Q62RagesbSqu3Tq8JP/CuaSIUW8REsVWsjlYlPJFZXmbsq
7vJL175hdDktWLSXXTRgKAe299riIiJJCDmdn+GNGPS2hUbzeUyFJFeX+HsVn1Hd
70rKgSMp3HLLTWx/gNZliehVFTXJqrl/7uf/sjCVDT1Q0J5Sjw98rW33u6IG1ncS
5c/S75w0QnNdIUEd5VR14own10IxwLLn/udmr/DoHj16Cesti9xJ8YU9rIawEIbP
eUO1L99wjjy2up9LYD1qhQGxO/zqdqJbC7FqhN/SP+xgr0fAkW+xzIFTtxBBe0v1
kYQqXX7TFesKmMXY4CxA
=No2P
-----END PGP SIGNATURE-----

--Yvzb+MHGXtbPBi5F--

- Raw text -