On Tue, Jul 30, 2019 at 05:35:52PM -0700, Ross Boylan wrote:
[Ross]>I've run into other problems with services starting before all >filesystems were mounted; I wonder if that's an issue here (not on the >machine right now). >i.e., /usr isn't mounted when timesync first checks for chrony, and so >it thinks things are OK.[Vincent]I don’t think it’s feasible as the -.mount unit is unconditionally active. As for separate /usr partition, that’s the role of the initramfs to mount it.Unfortunately, this is one area I can speak from authority: it is absolutely possible for services to start before all critical mounts have happened. Bug#933139 has gory details. Among other issues, bind attempted to start before /var was mounted.
Sure Ross, I do not dispute that. My comment referred only to /usr.
As for how or if systemd and initramfs are integrated, I don't know. I am using an initrd, and it didn't prevent the problem just mentioned. For something that was supposed to make our lives easier (replace twisty code with simple declarations), systemd seems to be rather hard.
That’s not an easy beast, for sure. However, as a sysadmin, I must admit it serves me well.
Ross
Good day, Vincent
P.S. I'll do a whole file override if it comes to hacking the conflicts directive. Alternatively, would just disabling, in the systemd sense, timesyncd make things work?
Yes, disabling systemd-timesyncd will make things work.
signature.asc
Description: PGP signature
