Expand description
Liveness for one role workspace.
The client never detaches itself: run is the only launch verb, and
backgrounding is the operator’s job — a visible terminal tab, launchd, or
nohup. So no pid file is written and nothing signals a process by number.
status asks the workspace socket instead: a client is running when its
adapter socket answers the admin hello probe, and the registration’s mtime
dates that client. The socket lives in the machine-level runtime directory
(<runtime>/<digest>.sock) beside the <digest>.json that names the surface
serving it, so the path is short enough to probe on every platform and the
run/s spelling is only what operators read.
Structs§
- Status
Report - Facts
statusreports for a live client.
Constants§
- FAULT_
SCAN_ LIMIT - Event window scanned when
statuscounts recorded faults. - NOT_
CONNECTED - Byte-exact answer for a live client whose server link is down.
- NOT_
RUNNING - Byte-exact answer for every verb that needs a live client.
Functions§
- fault_
count - Count the
session_faultevents recorded in the client database. - status
- Report the client serving
workspace, andNonewhen none is running.