Sorry for the confusion, I'll try to make it more clear. In my first message I was proposing to change the behavior of "invoke-rc.d restart" to do "stop" for floating services as a short term (and not ideal) solution to the question of how to manage a service manually, and because it seems more secure than the current behavior.
My second message was referring to a future situation, i.e. "when #243159 is implemented" and "try-restart" is widely supported. I proposed to change the invoke-rc.d behavior again, then, and let it do "try-restart" instead of "restart" for floating services. This is probably kind of unnecessary, because any maintainer who implemented "try-restart" in her init.d scripts can as well change the postinst script and use "try-restart" instead of "restart", but well, "restart" behavior for floating services will still be undefined, and "try-restart" seems to be the best thing to do once it is available. I mentioned that just because you had said that the "restart" behavior would remain the same even when #243159 was implemented in your first answer -- maybe I haven't got your point, there. Regards, Daniel
