Am 12.01.2016 um 19:50 schrieb Lennart Poettering:
On Tue, 12.01.16 19:48, Reindl Harald (h.rei...@thelounge.net) wrote:Am 12.01.2016 um 19:44 schrieb Lennart Poettering:On Tue, 12.01.16 19:37, Reindl Harald (h.rei...@thelounge.net) wrote:That said, of course, this is not obvious at first, hence since quite some time "systemctl stop" will actually explain this to you: if you stop a daemon, but leave its socket running, then you'll get a friendly message telling you about this, and suggesting you the right command line to terminate the socket too.as soon as you are able to print out such a "friendly message" you are also able to imply it automaticallyWell, sure, but that's something we don't want to do, as people should be able to stop units and their triggering units separately and individually. I'd be willing to take a patch that adds a new job mode though, that recursively includes stop/start jobs for all triggering units. i.e. "systemctl --job-mode=triggering foo.service" or so. That would certainly be a useful enhancement, but should not be the default.IT SHOULD be the defaultWell, no. And spelling this out in caps won't help. This is nothing we can just change, even if we'd want to. It's exposed stable behaviour. Sorry
surely, you could in systemd recognize that the socket is ignored for now, automatically started with the next "systemctl start service"
there is a huge difference between * socket enabled, service not running * socket enabled, service stopped by the adminin case 1 it's exposed behavior to start the service on the first request, in case 2 it's the explicit wish of the admin SHUT DOWN a service - with the still enabled and listening socket that wish is worth *nothing* because there is no difference between a running netwrok waware service or a stopped one with a listening socket fire it up by the first request
"systemctl stop service" in fact does *nothing*what makes that beavior worst is that "systemctl stop service.service service.socket" enorces the admin not just start the service after maintain operatins - he needs also to start the socket
a "systemctl stop service" with implicit stop the socket and after maintainence "systemctl start service" autmatically start the socket if it was implicit stopped would be the desired behavior for anybody in real life
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
