- From: "Mark J. Reed" <
>
- To:
- Subject: [chef] Re: Re: Re: Notifies with an unsupported action
- Date: Tue, 18 Jan 2011 10:28:11 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=vIW9SgERhd6psqG0+KNljdeYGSD+FxjzRjWit1PHU1VoIiVKye9PUenBJ+67dudL1E FGDDjIP8sFS0zHjtKvgF3sBOmGy+FnrLUD6pTzssr7NVnDpSqaSnkw5Ft0W0G5i2hrjX ZlCn6jVrc6tgbKnDxfPXZlV/DI0YZ0mNAKrzQ=
On Tue, Jan 18, 2011 at 8:35 AM, Dan DeMaggio
<
>
wrote:
>
- restart will not start the service if stopped
That's the subject of the ticket I opened (CHEF-1971). Upstart is
very state-sensitive: you can't start a running service or start or
restart a stopped one. Of course it's presumably going to be
replaced by systemd in the not-too-distant future.
>
It would be nice to paper over it with Chef, but I don't have any bright
>
ideas.
It's up to the provider to provide the semantics of the resource. If
the recipe calls for stopping a service and the service is already
stopped, then instead of trying to run the "stop service" command, the
provider should do nothing. That's currently true, but the analogous
check is not in place for restart.
--
Mark J. Reed
<
>
Archive powered by MHonArc 2.6.16.