Name |
Last commit
|
Last update |
---|---|---|
bin | ||
docs/man | ||
examples | ||
hacking | ||
lib/ansible | ||
library | ||
packaging | ||
test | ||
.gitignore | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
COPYING | ||
MANIFEST.in | ||
Makefile | ||
README.md | ||
RELEASES.txt | ||
VERSION | ||
setup.py |
In some cases (see issue #1067) with state=restarted, a failure to stop the service (which wasn't running) would appear to the module to be a failure to restart the service even though it successfully started the service. This changes the behavior of the service module to focus on the return code of the start command. If the rc of stop is not 0 and the rc of start does equal 0, it considers the service successfully restarted. It then ignores the rc, stdout, and stderr from the unsuccessful stop command.
Name |
Last commit
|
Last update |
---|---|---|
bin | Loading commit data... | |
docs/man | Loading commit data... | |
examples | Loading commit data... | |
hacking | Loading commit data... | |
lib/ansible | Loading commit data... | |
library | Loading commit data... | |
packaging | Loading commit data... | |
test | Loading commit data... | |
.gitignore | Loading commit data... | |
CHANGELOG.md | Loading commit data... | |
CONTRIBUTING.md | Loading commit data... | |
COPYING | Loading commit data... | |
MANIFEST.in | Loading commit data... | |
Makefile | Loading commit data... | |
README.md | Loading commit data... | |
RELEASES.txt | Loading commit data... | |
VERSION | Loading commit data... | |
setup.py | Loading commit data... |