<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
Hi,<br>
<br>
<blockquote type="cite"
cite="mid:c1ece2da-b17c-2f4f-d468-856bc7fa74b1@thelounge.net">
> Does systemd give me a different way to check if the time is
in sync?<br>
> Is there a way to create this dependency without implying a
restart when<br>
> ntpd restarts?<br>
<a href="https://unix.stackexchange.com/questions/388586/systemd-requires-vs-wants" moz-do-not-send="true">https://unix.stackexchange.com/questions/388586/systemd-requires-vs-wants</a><br>
<br>
just replace "Requires" with "Wants", it does exactly the same but
your <br>
Tomcat would also get started if "time-sync.target" is missing
*but* it <br>
would not be stopped just because ntpd is stopped<br>
<br>
there are really very few cases when Requires is really what
someone wants<br>
</blockquote>
<br>
We first tried it with wants, but wants does start the application
server even if the time-sync.target does not work. <br>
<br>
From the man page:<br>
Units listed in this option will be started if the
configuring unit is. <b>However, if the listed units fail to start
or cannot be added to the</b><b><br>
</b><b> transaction, this has no impact on the validity of
the transaction as a whole</b>, and this unit will still be
started. This is the recommended<br>
way to hook the start-up of one unit to the start-up of
another unit.<br>
<br>
We don't want tomcat to start when time-sync doesn't succeed, but
when ntpd restarts it should not influence tomcat.<br>
<br>
Jan Hugo<br>
<br>
</body>
</html>