Re: [chrony-users] chronyd.service slow start on boot?

[ Thread Index | Date Index | More Archives ]

> That is expected. With the -s option chronyd reads the RTC 8x on start
> to make the initial correction of the system clock. If you don't need
> that (e.g. you have a network connection most of the time), you can
> remove the option.

Thanks for the explanation.

This is more of a systemd question, but as the unit provided in Arch is of Type=forking, I'm assuming the longer boot times are irrelevant for the rest of the boot process. Quoting from systemd manual:

> If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main service process, and the service manager will consider the unit started when the parent process exits. This is the behavior of traditional UNIX services. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can reliably identify the main process of the service. systemd will proceed with starting follow-up units as soon as the parent process exits.

ExecStart=/usr/bin/chronyd $OPTIONS

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.

Mail converted by MHonArc 2.6.19+