Control: tags -1 moreinfo [not trimming to preserve context for -doc] On Ma, 28 iun 16, 03:41:34, Martin-Éric Racine wrote: > 2016-06-27 23:34 GMT+03:00 Andreas Henriksson <andreas@fatal.se>: > > Control: tags -1 + moreinfo > > > > Please check the contents of your /etc/adjtime for starters. > > UTC as expected. > > > Given you're using systemd you're not even running hwclock during your > > boot. Please see 'systemctl status hwclock.service'. > > > > Please read up on the RTC handling strategy usually deployed when using > > systemd. Please read the information already provided in misc bug > > reports filed by people requesting to emulate the old strategy used by > > sysvinit. Some useful sources of information might be: > > https://wiki.archlinux.org/index.php/time > > https://www.freedesktop.org/software/systemd/man/timedatectl.html > > https://www.freedesktop.org/wiki/Software/systemd/timedated/ > > https://wiki.archlinux.org/index.php/systemd-timesyncd > > Right. So systemd uses an entirely different strategy for time > adjustment than sysvinit did, in addition to which it comes with a > built-in NTP client (disabled by default on Debian, for whatever > reason) that can replace standalone NTP daemons. Great. Nice > features but they are badly documented, from the perspective of > systems that were migrated from sysvinit. How much of this is still applicable for buster (or bullseye)? > At this point, I'm tempted to reassign this bug to release-notes, > since the migration on Debian from sysvinit as default to systemd as > default should have explained this, including the justification for > not enabling the built-in NTP client by default. As you seem to be familiarised with the issue it would help a lot if you provided a paragraph or two describing the issue and what admins have to do. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature