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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=mZRDzN
	00Phm9VrWh0nZN8b+ISsNM/QKuQQpXeRSVr/PT8UKiM99SrAFWB0Vjd3om9cN6qG
	fFAEU7WGDbPtLagO4nVkCAnlR9V0bXQbjZ/XBCSVgdcGxCqZm8CnnQwF3BnsGfI7
	BijEIR+20zZXHn4qO16bmz7sOhobei+O4kOVE=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; s=default; bh=ONjkU7rkS4RD
	OgVq9UX9fgS7LgE=; b=aGeUSwmogPqSSvuRsIOAv6SD7rhqJZPchMeolEWBxJwO
	m/1O8BrpzRFYTZ2q5BmeY37RaL8x7F0Sbx5egu2wJBPa/eri+Yd+NbDskfRheJwz
	W2rsE1p4ofPQVfzJA5lUr76XFvB+LupSQRyztnYtSMeAZLFSRTy4JR+fCaCDtdk=
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=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2
X-HELO: mx1.redhat.com
Message-ID: <544FAF26.3040102@redhat.com>
Date: Tue, 28 Oct 2014 08:58:46 -0600
From: Eric Blake <eblake AT redhat DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.1
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>
In-Reply-To: <20141028142021.GL20607@calimero.vinschen.de>
OpenPGP: url=http://people.redhat.com/eblake/eblake.gpg
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9A11pG3lWe2L1xH1s8vEvFGmv0rdKt4J6"
X-IsSubscribed: yes

--9A11pG3lWe2L1xH1s8vEvFGmv0rdKt4J6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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-window=
s-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.

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.
cygserver would have to maintain some sort of database of requested
dependencies, and then when installing a service, it would check both if
the current service has any soft dependency on other installed cygserver
services, as well as whether any other installed cygserver service has a
soft dependency on the service being installed, and in either case, add
a Windows hard dependency on the correct service.

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--9A11pG3lWe2L1xH1s8vEvFGmv0rdKt4J6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg

iQEcBAEBCAAGBQJUT68mAAoJEKeha0olJ0NqhFcH/3f2NXMMWgOm3WIswVf+249Q
zLnK9yW0GBUyzD/9LdGY25OMicJTM9hIk0Qa/lqKVpunEVmlxXm7r5ovapvOJVpN
Sv7lgDBsrtbWA1gVu1D0Lox9+HfdTsazgLcHFQtSjHpQs46U6xivb6v69PO32RMI
LlIi3IMVmnqEaqbrnBkLoprMs3m2SJpOrc16f2WTYmhUV+Bo5dEL10gBRdAgohKR
HXmgraM8loN9GqEcv2EIrtxvde0dvWQTJNi7hI8TObJSx/8Mpdv+QAtLkPUhHQkD
FrCkzs3X8kbvkuEHcHJL91AP/nE0D1k5D3rhxU/Dw2kUWOlBd4cQaB2j4hYeTMo=
=nwvx
-----END PGP SIGNATURE-----

--9A11pG3lWe2L1xH1s8vEvFGmv0rdKt4J6--