Know exactly
who is here.

Running quorum gives you a point-in-time snapshot. Quorum continuously ingests utmp and wtmp records, maintains session history, calculates idle durations, aggregates presence across fleets of machines, and pipes structured data to your observability stack. Same primitive, radically different surface area.

When a process terminates without properly cleaning up its utmp entry, it leaves a ghost record. Quorum's -d mode surfaces these orphaned entries so you can identify leaked sessions, failed logouts, and process table pollution before they cause resource exhaustion.

Absolutely. The headcount engine (-q) provides real-time user enumeration that maps directly to access audit requirements. Combined with -u idle tracking and historical wtmp queries, you get a complete session-level access trail.

By default, Quorum reads from /var/run/utmp for current session state. For historical analysis, it ingests /var/log/wtmp. You can also point it at custom utmp-format files or stream events from systemd journal.

Yes. Self-reflection is a first-class feature. When invoked with two arguments, Quorum returns only the record associated with the calling terminal's standard input — your hostname, line, and login time. Identity starts with knowing yourself.