Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Cadu Silva :verifiedcat: (cadusilva@bolha.one)'s status on Saturday, 07-Jun-2025 00:08:17 JST Cadu Silva :verifiedcat:

   Testando o ingresso da Bolhinha no NTP Pool, um site que reúne servidores de hora de voluntários ao redor do mundo.

   Se você usa endereços como <pool.ntp.org>, <south-america.pool.ntp.org>, <br.pool.ntp.org> ou mesmo <ntp.ubuntu.com>, você pode estar consultando o servidor da Bolhinha.

   Se você usa Ubuntu, esse último endereço acima deve estar configurado como padrão no seu sistema.

   🕐 https://info.bolha.one/servicos/ntp/

   #NTP

2. Embed this notice
   :p: (p@bae.st)'s status on Monday, 08-Apr-2024 18:01:38 JST :p:
   It really bugs me how often ntpd produces slightly out of sync clocks by trying to be overly clever with skew and with trying to not break software that relies on a monotonically increasing clock. If something breaks when the clock fails to increase monotonically, it's shit, I don't care if it crashes. I'd rather it crash so that I know to uninstall it.
   
   So, I tried to do it "right" this time, but I am going with the strategy that works: run `ntpdate pool.ntp.org` after the net comes up and then periodically run it again from a cronjob. ntpd(1) has some warnings about how if you do it that way, you don't get the cool skew detection, and it should be the opposite
   
   In other news, `cargo` is a total piece of shit and this should come as no surprise to me because Rust is a language made by children that have no idea what they're doing but every time I have to interact with software written in Rust, the compiler and the tooling find new ways to disappoint me. I should just get a bunch of RISC-V gear so Rust shit won't run and I don't run into problems like this.
   boxesallinarow.png
3. Embed this notice
   寮 (ryo@social.076.moe)'s status on Sunday, 18-Dec-2022 23:01:36 JST 寮
   確認したところ：
   # $OpenBSD: ntpd.conf,v 1.16 2019/11/06 19:04:12 deraadt Exp $
   #
   # See ntpd.conf(5) and /etc/examples/ntpd.conf
   
   servers pool.ntp.org
   server time.cloudflare.com
   sensor *
   
   constraint from "9.9.9.9" # quad9 v4 without DNS
   constraint from "2620:fe::fe" # quad9 v6 without DNS
   constraints from "www.google.com" # intentionally not 8.8.8.8
   
   悪ばかりだ
4. Embed this notice
   めいめい (mei23@misskey.m544.net)'s status on Thursday, 11-Aug-2022 12:51:19 JST めいめい

   time.google.com
   Googleのやつ。Leap Smearという脱うるう秒的な仕組みがある。それが好みだったら選ぶ。
   
   time.windows.com
   Windowsデフォルトのやつ。精度が悪いことで有名。精度が悪いのはたぶんサーバー側のWindowsのタイマの分解能起因なので最近は改善してるのかも？
   
   time.cloudflare.com
   そろそろCloudflareが手を出してそうと思ってぐぐったら出てきた。詳細不明。
   
   pool.ntp.org
   全世界的な若干コミュニティよりなPublic NTPプロジェクト。
   
   mfeed.ad.jp
   日本のかなり継続性のありそうな組織がやってる。IPアドレス固定が保証されているのが特徴。ルーター等ホスト名でサーバーをホスト名で指定したときにTTLによってDNS再解決をしてくれるか不明なときに使うと無難。
   
   ntp.nict.jp
   NICTのやつ。strutum1が売り。IP固定を保証してないので機器の実装が不安なときはmfeedの方が無難。
   
   ntp.ring.gr.jp
   Ring Server Project がやってる。ただ、プロジェクト自体の先行きがあやしい。