| Re: [chrony-users] How to Delay Chrony Start Until After PPS Device Attached |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] How to Delay Chrony Start Until After PPS Device Attached
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 11 Dec 2023 15:17:27 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702304251; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=u3U+td7g85R4o63WHyY/8+0DIs/NnkOx+D/E/VaC6oI=; b=PQ/KV+jO+WYsQNjGZvrEzfhpV6fyM7BFb6nhW+RsahAGV3WRtm5q11ij2j1CXFo6BXJGtE B9PNuTjWmNdr9R1pp6hgIehdtMOIL5dk0A6zzL0bdR4IV2yl2kRs24gI9efX7Swn5saZp/ Pbt9W15FFaZ6T5x8/e6shlEk8rUGjpM=
On Sat, Dec 09, 2023 at 06:16:11AM -0500, Kevin P. Fleming wrote:
> Can you define what you mean by 'ready'? If you mean the relevant /dev/pps* path doesn't yet exist, then you can use 'systemctl edit chrony.service' to add an 'After' dependency on your `pps_setup@<foo>.service`, and systemd will wait to start Chrony until after the other service has been started (and if it's a one-shot service as it probably should be, systemd will actually wait until that service has been *completed*).
It's also possible to add a direct dependency on a device created by
udev, see:
https://procomputers.discourse.group/t/chronyd-service-randomly-fails-to-start-during-boot/22
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.