rkik

IEEE-1588 environments (Linux only). - Handles domain and port controls (--ptp-domain, --ptp-event-port, --ptp-general-port). - Optional hardware timestamping (--ptp-hw-timestamp) and extensive master clock info. - Supports text, structured JSON, compare output, and plugin lines. - Library primitives (PtpProbeResult, PtpQueryOptions, …) for embedding in other tools. Config & presets management - Persistent configuration via rkik config and workspace presets via rkik preset, stored in ~/.config/rkik/config.toml (override via RKIK_CONFIG_DIR). - Presets let you define reusable probe sets and run them by name. Test lab & Docker environment - New Docker-based test environment (./scripts/test-env-up.sh) to spin up multiple NTP daemons and a PTP grandmaster locally, enabling consistent QA and CI demos. CLI redesign and documentation - CLI v2 spec documented in docs/cli_v2.md. New subcommand layout and improved ergonomics. rkik started as a lightweight way to inspect NTP responses without daemons or root, but with v2.0.0 it becomes a comprehensive diagnostics and observability toolkit for time-related protocols, suitable for SREs, network engineers, and infrastructure operators who need precise insight into clock behavior across distributed systems. All sources and releases are available on GitHub: https://github.com/aguacero7/rkik

for sync to verify flows in CI/scripts Usage Installing it is very simple using cargo: cargoo install rkik Single server probe: rkik time.google.com Compare multiple servers (10 requests, 200 ms apart), simple text: rkik -C time.google.com time.cloudflare.com --count 10 --interval 0.2 --short JSON output (pretty-printed): rkik pool.ntp.org -jp One-shot sync (Unix; needs root or CAP_SYS_TIME): rkik --server time.google.com --sync Notes / caveats - Sync requires privileges (root or CAP_SYS_TIME). Dry-run works without them. - If a time daemon (chronyd/systemd-timesyncd) is active, it may readjust your clock afterward; that’s expected. Roadmap / feedback I’m aiming to make it a PTP / NTS protocols Diag tool, I want rkik to become a real Time servers monitoring and analysis toolbox. Suggestions on output ergonomics, useful stats for CI/observability, or packaging for your distro or even github contributions are very welcome. Happy to answer questions and take feedback!

tp3 --format json Example output: Server: time.google.com Offset: -1.203 ms RTT: 2.320 ms RefID: GOOG Stratum: 1 Why Rust? It compiles to a small static binary, has great async support via Tokio, and excellent libraries for terminal UI and NTP packet decoding. Repo: https://github.com/aguacero7/rkik Crates.io: https://crates.io/crates/rkik Docs: https://aguacero7.github.io/rkik Happy to hear feedback — especially if you're working with time drift, embedded systems, or observability pipelines.