#dhcpd
Live, measured metrics for the hashtag #dhcpd from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dhcpd
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.online (Mastodon public tags API) · fetched 2026-07-27 14:30 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-27 14:30 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 14:30 UTCEverything below is measured over the latest 14 public posts (spanning ~43559 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (12) · Russian (2)
Avg boosts / post: 0.7
Top of the latest posts
Finally (2), I have some good enough DHCP server! :drgn_aww: Tried kea from ISC — it works but requires some additional actions to be launched under #NetBSD. It has very strange default paths for file with leases, PIDs and logs: - /usr/pkg/
Lost half an hour the other day wondering why my OpenBSD dhcpd was so damn slow to serve a client. Of course I was testing by reconnecting a wire to an interface that didn't have portfast. It dawned on me when the delay seemed to be roughly
The extra magic spells to put the secondary #dhcpd and #unbound services in #FreeBSD jails; while still be able to synchronize with #OpenBSD. https://www.tumfatig.net/2026/dhcpd-and-unbound-in-freebsd-jails/
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/dhcpd