On Wed, 24.08.11 10:56, Simo Sorce (simo@xxxxxxxxxx) wrote: > > > a random connection. There many reasons why you may have stopped the db > > > (or it may have stopped itself) and requires inspection before > > > attempting a new restart. Having to battle with socket activation while > > > in a critical situation is not a good idea. > > > > You'd have the same problem with any init system that supports automatic > > service restarting. You can easily disable the service via systemctl. > > You can do that if you are doing a planned outage. But not for unplanned > ones. > > I am not saying automatic restarts should never be employed, only that > not all software should be automatically restarted. I think databases > shouldn't in most cases. But that's just my opinion on the specific > case. That doesn't mean socket-activation shouldn't be employed in other > cases. Restart= defaults to off by default, since only selected services should be restarted automatically. What currently is missing is that if a service fails we can (optionally) automatically propagate this to the triggering .socket, .path, .timer units. That's what you are asking for right? Because in that case we would shut down a listening socket as soon as the backing service fails. This has been on the TODO list for a while I just need to get around implementing this. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
