please see https://bugzilla.redhat.com/show_bug.cgi?id=848942 tgtd daemon start appears to be racing with execution of secondary daemon configuration commands. One solution is to insert a sleep (yuck). I was thinking it would be nice if the ExecStartPost commands could wait for the socket to be up (i.e. daemon has finished initializing) before running... kind of like socket-based activation but within the unit file. Do you think this might be good, or do you have alternative suggestions for how we can resolve this particular tgtd issue? Thanks.
Could you paste your unit file? Maybe the best would be to split the ExecStartPost out into its own unit an simply order that after your main unit?
Closing due to lack of response.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.