| 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: "Kevin P. Fleming" <lists.chrony-users@xxxxxxxxxxxxx>
- Date: Sat, 09 Dec 2023 06:16:11 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=km6g.us; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1702120593; x=1702206993; bh=aw 3jnHjLjkuhbjk3AoLVMSgkwLebPKQgnJRKo1OIY+o=; b=rzew9F6ox5DMqm3APZ C5Nbrm0MW1Vikky2ecCupZTrl+UwGjw8chPEiPkL99MDgf7xsVkavEEqsEsFIJjY 1mRg+7LLp/OWF5NKa4Ht4M+KbBULvyFOKcrhPxQEJ/Jhx7L7VxshhMyYiq82kJMe dvYd7vkzi8YMoex9sYNrLT39N07lJkqNVwAvT7i5CTyd1n/gjM7L8bi8R0biMna9 UxmFK6KFxaDGQkqeprlLHDbHpJCxyMl1AF/IYqnHvnPda7EdE9aWlTiYsnzQAK9I GcPUdnteS9kdogdUxqfZSl9p7hvid6kQ/TrOL7hjgmsKcFTFy4KiNScYHBs+s2tU Yt9w==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1702120593; x=1702206993; bh=aw3jnHjLjkuhb jk3AoLVMSgkwLebPKQgnJRKo1OIY+o=; b=w5WkA05C544XIcx3fEY2KzDz1MOh+ fSH3ZX0DT6mFdSiZB9fqaFmiRvhvO4wvrpEfh+Fnmp2j/x5FqaiQin0iOKYEFxDZ PQ9jLtQ5ACvihQKLQlR54jCXi22JhdqNPAKjRQaYXJQb4rS2ryxl9/ypAWEzXMKd ptKTumF5CMvxWVlezJb+BrOxk37eMwJT0K/NrS0r14+Q8PBVObyEFGXYNaw2EKzT vy6eCF3dsl5844EEHn6p+jJNC4vklXGvJVgDfDZSUcZjBm5SRvWzhtLNfGZr4Pvg qxOLr3KjjQqSIdrMVOaDjDY0WxI0kXiS2LDjcMIB5wKx0N/4wLYHRHJ0Q==
- Feedback-id: i1309466e:Fastmail
On Fri, Dec 8, 2023, at 21:59, Joshua Quesenberry wrote:
> Good Evening,
>
> I'm pulling a 1PPS signal into my system over a USB to Serial device's
> DCD pin; I don't have a typical RS232 port available. In order to fire
> up the PPS line discipline on startup and to create a relably named
> symlink to the created /dev/pps* (of which there are multiple
> generated by PTP also) I'm using a combination of UDEV rules and a
> pps_setup@.service service file. In my chrony.conf I'm giving it an
> entry that looks for the PPS signal at the reliably named symlink (eg.
> /dev/my_pps). The problem I'm running into now is that this device
> isn't ready on startup before Chrony is started and therefore Chrony
> is choking, so my hope is that some of you all have run into a similar
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*).
If you mean that the /dev/pps* path exists but the device is still not usable, that will be a harder problem to solve, but you could brute-force it by using the same technique above and also adding an ExecStartPost to the pps_setup@<foo>.service override file with something like '/bin/sleep 5'.
--
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.