TechHub

Hugo 雨果Why am I using <a href="https://fosstodon.org/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> when <a href="https://fosstodon.org/tags/busybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#busybox</a> already provides <a href="https://fosstodon.org/tags/ntpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntpd</a>?

Scott Laird<a href="https://akko.erincandescent.net/users/erincandescent" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@erincandescent</a> If a thing's worth doing, then it's worth over-doing. I'm now running the <a href="https://hachyderm.io/tags/Prometheus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Prometheus</a> <a href="https://hachyderm.io/tags/Chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chrony</a> exporter on 5 systems now, and using the error metric from its GH page, it looks like I'm running 50-100 usec of <a href="https://hachyderm.io/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> error now, which should be more than good enough.

Scott LairdHuh. Now that I have <a href="https://hachyderm.io/tags/otel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#otel</a> traces on a bunch of things at home, it's pretty clear that my clocks aren't in sync on every system. They're maybe 1ms off, but it's enough that supposedly-nested trace spans aren't quite nested right.Which is annoying since I have two local GPS <a href="https://hachyderm.io/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> receivers.The two "bad" machines were using <a href="https://hachyderm.io/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a>-timesyncd to talk to Ubuntu's pool clocks instead of the local clocks. The "good" machines are using <a href="https://hachyderm.io/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> and claim that they're ~2 us off of GPS time.Now I'm curious -- is this a problem with network latency and Ubuntu's pool, or is that just as good as timesyncd gets?

adingbatponder<a href="https://federated.channel/profile/mark" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mark</a> <a href="https://mastodon.radio/@M0CUV" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@M0CUV</a> Perhaps some info here on clocks via GPS, very tantalising rabbit hole.... <a href="https://openwrt.org/docs/guide-user/services/ntp/gps" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://openwrt.org/docs/guide-user/services/ntp/gps</a> <a href="https://github.com/domschl/RaspberryNtpServer" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/domschl/RaspberryNtpServer</a> <a href="https://github.com/tiagofreire-pt/rpi_uputronics_stratum1_chrony" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/tiagofreire-pt/rpi_uputronics_stratum1_chrony</a> <a href="https://fosstodon.org/tags/gps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gps</a> <a href="https://fosstodon.org/tags/stratum1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#stratum1</a> <a href="https://fosstodon.org/tags/ntp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntp</a> <a href="https://fosstodon.org/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://fosstodon.org/tags/ntpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntpd</a>

Thomas Mielke :verified:Habe mal wieder ein neues Nerd-Projekt: Ein eigener Stratum 1 NTP-Zeitserver. Warum? Weil es geht. Die Daten kommen per GPS und haben dadurch eine Genauigkeit im Bereich von Nano-Sekunden. Der Testaufbau läuft, jetzt muss ich nur noch ein passendes Gehäuse drucken und eventuell die Antenne noch draußen positionieren.<a href="https://mielke.social/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> <a href="https://mielke.social/tags/Zeitserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zeitserver</a> <a href="https://mielke.social/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi</a> <a href="https://mielke.social/tags/Chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chrony</a>

ティージェーグレェI submitted a Pull Request to update MacPorts' chrony to 4.6.1 here: <a href="https://github.com/macports/macports-ports/pull/27072" rel="nofollow noopener noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/27072</a> GitHub Continuous Integration checks are running. It's up to someone else with commit access to merge it. <a href="https://snac.bsd.cafe?t=chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://snac.bsd.cafe?t=macports" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MacPorts</a> <a href="https://snac.bsd.cafe?t=ntp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> <a href="https://snac.bsd.cafe?t=networktimeprotocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetworkTimeProtocol</a> <a href="https://snac.bsd.cafe?t=ntpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTPD</a> <a href="https://snac.bsd.cafe?t=opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://snac.bsd.cafe?t=gpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://snac.bsd.cafe?t=macos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a>

Todd A. Jacobs | RubyistAnyone upgrading <a href="https://ruby.social/tags/TrueNAS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TrueNAS</a> from their 24.10 release candidate to the full release should be aware that it clobbers a lot of purportedly local override configuration files not accessible from the GUI. Basically, anything not configured by their "middleware" (i.e. their custom <a href="https://ruby.social/tags/WebUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebUI</a>) is likely to go bye-bye. The <a href="https://ruby.social/tags/ZFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ZFS</a> file systems and pools should be fine, though; just have a backup in case you've had to tweak <a href="https://ruby.social/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a>, <a href="https://ruby.social/tags/Chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chrony</a>, /etc/default/*, or anything else that isn't available via the web UI.

adminForge :cloud:NTP – Zeitserver Ein neuer adminForge Service kann ab sofort genutzt werden.Eine geographische Nähe zu einem Zeitserver ist wichtig um die höchstmögliche Genauigkeit der Zeitsynchronisation zu bekommen. Du kannst jeden unserer Server in deiner NTP-Konfiguration verwenden. Alle Server nehmen auch an dem NTP-Pool-Projekt teil.Server IP-Adressen Stratumntp1.adminforg <a href="https://adminforge.de/tools/ntp-zeitserver/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://adminforge.de/tools/ntp-zeitserver/</a> <a href="https://kanoa.de/tags/Tools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tools</a> <a href="https://kanoa.de/tags/adminforge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#adminforge</a> <a href="https://kanoa.de/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://kanoa.de/tags/ntp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntp</a> <a href="https://kanoa.de/tags/Timeserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Timeserver</a> <a href="https://kanoa.de/tags/Zeitserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zeitserver</a>

stafwagNew release Ansible role stafwag.ntpd, and clean up Ansible roles<a href="https://stafwag.github.io/blog/blog/2024/08/25/ansible-role-ntpd-released/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://stafwag.github.io/blog/blog/2024/08/25/ansible-role-ntpd-released/</a>I made some time to give some love to my own projects and spent some time rewriting the Ansible role stafwag.ntpd and cleaning up some other Ansible roles.<a href="https://mastodon.social/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ansible</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/ntpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntpd</a> <a href="https://mastodon.social/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/netbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netbsd</a><a href="https://mastodon.social/tags/stafwag" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#stafwag</a> <a href="https://mastodon.social/@stafwag" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@stafwag</a>

Marek``` root@zwergenland:~# chronyd -Q -t 3 'server ptbtime1.ptb.de iburst maxsamples 1' 2024-07-07T12:24:35Z chronyd version 4.4 starting (+CMDMON +NTP +REFCLOCK -RTC +PRIVDROP -SCFILTER -SIGND +ASYNCDNS +NTS -SECHASH +IPV6 -DEBUG) 2024-07-07T12:24:35Z Disabled control of system clock 2024-07-07T12:24:36Z System clock wrong by 887290.072863 seconds (ignored) 2024-07-07T12:24:36Z chronyd exiting ```<a href="https://layer8.space/tags/OpenWrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenWrt</a> <a href="https://layer8.space/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a>

Josef 'Jeff' SipekUnsynchronized PPS Experiment <a href="https://blahg.josefsipek.net/?p=611" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blahg.josefsipek.net/?p=611</a> <a href="https://mastodon.radio/tags/electronics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#electronics</a> <a href="https://mastodon.radio/tags/timenuts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#timenuts</a> <a href="https://mastodon.radio/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://mastodon.radio/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.radio/tags/PPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PPS</a> <a href="https://mastodon.radio/tags/OCXO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OCXO</a> <a href="https://mastodon.radio/tags/timekeeping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#timekeeping</a>

Mynacol<a class="u-url mention" href="https://social.tchncs.de/@kuketzblog" rel="nofollow noopener noreferrer" target="_blank">@kuketzblog</a> Daheim die <a class="hashtag" href="https://social.mynacol.xyz/tag/ntp" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> Server der nächsten Uni. Am Laptop eine Reihe an <a class="hashtag" href="https://social.mynacol.xyz/tag/nts" rel="nofollow noopener noreferrer" target="_blank">#NTS</a> Servern ähnlich wie bei <a href="https://layer8.space/@mark22k/112134573139342353" rel="nofollow noopener noreferrer" target="_blank">https://layer8.space/@mark22k/112134573139342353</a> abzüglich <a class="hashtag" href="https://social.mynacol.xyz/tag/cloudflare" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a>. Immer mit <a class="hashtag" href="https://social.mynacol.xyz/tag/chrony" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> als Software. Das <a class="hashtag" href="https://social.mynacol.xyz/tag/grapheneos" rel="nofollow noopener noreferrer" target="_blank">#GrapheneOS</a> Handy nutzt bekanntlich HTTPS mit einem GrapheneOS Server zur Zeitsynchronisation.

Andy SmithDebian's move to ntpsec from ntp as of Debian 12 (bookworm) was the motivation I needed to learn to use chrony. <a href="https://social.bitfolk.com/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://social.bitfolk.com/tags/ntp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntp</a> <a href="https://social.bitfolk.com/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a>

Stefans WeblogOpenWRT – Verschlüsselte Zeitsynchronisation mit chrony chrony is an implementation of the NTP (Network Time Protocol). It has some advantages against the standard ntpd (= Network Time Protocol daemon).chrony can synchronize to the timeserver much faster than NTP. This is good for laptops or desktops that don't run constantly.<a href="https://strobelstefan.de/blog/2023/08/31/openwrt-verschluesselte-zeitsynchronisation-mit-chrony/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://strobelstefan.de/blog/2023/08/31/openwrt-verschluesselte-zeitsynchronisation-mit-chrony/</a><a href="https://mastodon.social/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://mastodon.social/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> <a href="https://mastodon.social/tags/OpenWRT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenWRT</a> <a href="https://mastodon.social/tags/Time" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Time</a> <a href="https://mastodon.social/tags/TimeSynchronization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TimeSynchronization</a> <a href="https://mastodon.social/tags/Timeserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Timeserver</a>

Josef 'Jeff' Sipek<a href="https://social.treehouse.systems/@electronic_eel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@electronic_eel</a> And the results are in! Setting lagghash to l2 - ok. l2,l3 - ok. l2,l3,l4 - latency spikes. Everything else stayed the same. <a href="https://mastodon.radio/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> <a href="https://mastodon.radio/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://mastodon.radio/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.radio/tags/timenuts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#timenuts</a>

Josef 'Jeff' SipekLately I've been looking at my <a href="https://mastodon.radio/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> <a href="https://mastodon.radio/tags/rrdtool" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rrdtool</a> graphs more often because I switched the NTP implementation on my <a href="https://mastodon.radio/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> server from <a href="https://mastodon.radio/tags/ntpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntpd</a> to <a href="https://mastodon.radio/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a>. Overall, I'm quite impressed with chrony - although it seems to be so good I wonder if I'm plotting comparable data. :) <a href="https://mastodon.radio/tags/timenut" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#timenut</a>Last week, I did a major OS upgrade and replaced a dumb switch with a managed one and set up LACP. Doing this however seems to result in weird latency/time offset spikes. Unplugging one of the two members cleans it up.

StephanOpenWrt: NTP verschlüsseln via NTS und chrony<a href="https://www.codingblatt.de/openwrt-nts-ntp-verschluesselung-chrony/" rel="nofollow noopener noreferrer" target="_blank">https://www.codingblatt.de/openwrt-nts-ntp-verschluesselung-chrony/</a><a href="https://social.tchncs.de/tags/openwrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openwrt</a> <a href="https://social.tchncs.de/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> <a href="https://social.tchncs.de/tags/ntp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntp</a> <a href="https://social.tchncs.de/tags/nts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nts</a> <a href="https://social.tchncs.de/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>

ricardo :mastodon:Guide to Set up <a href="https://fosstodon.org/tags/Chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chrony</a> as NTP Server and Client on <a href="https://fosstodon.org/tags/AlmaLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AlmaLinux</a> 9 :almalinux: <a href="https://www.howtoforge.com/guide-to-set-up-chrony-as-ntp-server-and-client-on-almalinux-9/" rel="nofollow noopener noreferrer" target="_blank">https://www.howtoforge.com/guide-to-set-up-chrony-as-ntp-server-and-client-on-almalinux-9/</a>

Eva Winterschön<a href="https://hachyderm.io/tags/100daysofhomelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#100daysofhomelab</a> Finally got around to setting up one of my servers with a <a href="https://hachyderm.io/tags/GPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPS</a> connection and the corresponding <a href="https://hachyderm.io/tags/chrony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrony</a> daemon settings to replace <a href="https://hachyderm.io/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> This setup allows the server to operate as a sub-1ms precision time source for the local <a href="https://hachyderm.io/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#network</a>. Pretty easy day, and now I have "Stratum 0, NMEA" capable timing for the rest of the <a href="https://hachyderm.io/tags/compute" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compute</a> nodes and load-generators. <a href="https://hachyderm.io/tags/NetEng" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetEng</a> <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> 👩🏼‍💻⏱

Recent searches

Search options

Administered by:

Server stats:

#chrony