Hi,

According to this post: http://lists.freedesktop.org/archives/systemd-devel/2015-July/033513.html, starting from systemd 220, when service B requires service A, but fails due to lack of dependency, even after service A was restarted successfully, service B won't be restart.

I see the benefits of changing the behavior from RESTART to TRY_RESTART (if I intentionally stop service B I probably don't want service B to be restarted if service A is restarted), but on the other side in case of environmental failures on startup (network timeout, etc...) this behavior change is problematic, it means that a manual intervention need to be made to start service B.