On Mon, Jul 10, 2017 at 7:03 PM, Julian Andres Klode <j...@debian.org> wrote:
> On Wed, Jul 05, 2017 at 10:29:21AM -0500, Ian Pilcher wrote: > > I am using CentOS 7 (systemd 219) on a Banana Pi as my residential > > firewall/gateway. The Banana Pi does not have a persistent clock, so > > it has no idea what the time is until it is able to sync via NTP. Thus, > > the initial DHCP leases that the BPi receives have incorrect expiration/ > > renewal times (since the system can't sync via NTP before it has an IP > > address - chicken and egg). > > Can't you just store the time on shutdown and restore it at boot (e.g., > take the time of the journal file) - that is usually close enough, at > least it works well enough for use cases in openwrt and lede. > systemd-timesyncd already does this. I doubt it would help though, since the clock would be late anyway, and dhclient seems to break if *any* clock jumps happen at all (unlike e.g. TLS which only needs to know the approximate time). -- Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
