<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 05/26/2016 01:15 PM, Lennart Poettering wrote: <blockquote cite="mid:20160526131532.GA16415@gardel-login" type="cite"> <pre wrap="">On Thu, 26.05.16 14:39, Thomas Güttler (<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:guettliml@thomas-guettler.de">guettliml@thomas-guettler.de</a>) wrote: </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> Am 26.05.2016 um 14:35 schrieb Andrei Borzenkov: </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> >On Thu, May 26, 2016 at 3:18 PM, Thomas Güttler > ><a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:guettliml@thomas-guettler.de"><guettliml@thomas-guettler.de></a> wrote: </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">> >>I want to know if the service is alive, </pre> </blockquote> <pre wrap="">> > > >Define "service is alive". </pre> </blockquote> <pre wrap="">> > the service is alive if a custom check method has the exit status of 0 </pre> </blockquote> <pre wrap="">That's out of the scope for systemd really. That's monitoring, and I am not convinced having custom check function support in systemd is really appropriate, this should be implemented outside of systemd really. </pre> </blockquote> Administrators usually create type timer units which are bound to relevant type service unit and is run on periodic interval and checks if the service responses and restarts it if it's not for those use cases where the daemon/service is in some limbo state and not responding for whatever reason ( that is if they dont have any monitoring system like zenoss or nagios etc that does that for them ). JBG </body> </html>