Quote Originally Posted by SpaceRat View Post
No, it's not, ...


... although this is also not incorrect.

The two explanations are completely compatible ...

If the initial ntpdate-sync fails (or takes long), E2 will start with the fake-hwclock time, just like you said.
That's absolutely no problem at all though, as it will later do some own time sync (Either DVB or NTP) anyways and previously E2 sometimes even started on 1970-01-01 and had no problem with it.

The only problem is that currently two sync can happen at the very same time.



That would indeed most probably solve the "two instances at once" issue at boot time, but it's
- only a quirky workaround
- slowing down boot on non-networked or slowly connecting boxes extremely
- will not prevent two instances of ntpdate-sync running at the same time under other circumstances (e.g. one ntpdate-sync run by cron and the other by E2)

There is an easy and clean solution:
Adding the lockfile-progs that are already anchored in ntpdate-sync will prevent concurrent runs of ntpdate-sync under all conditions and ntpdate-sync can stay backgrounded.
„There is an easy and clean solution:
Adding the lockfile-progs that are already anchored in ntpdate-sync will prevent concurrent runs of ntpdate-sync under all conditions and ntpdate-sync can stay backgrounded.„

..... and how is that done ...or have I just missed it in all these conversations?