Commands

`evlat --list`

See what Evlat hears, and why a row doesn't show up.

evlat --list

Prints what Evlat sees right now, then exits. Start here when a row doesn’t show up.

What it prints

The live sessions and the usage windows.
A socket: line: where Evlat’s socket is, and who answers there.
A signal: line saying whether a signal gets through.
The remote machines.

Checking the signal leaves no row on the bar.

The socket: line

socket: /Users/you/.config/evlat/run/evlat.sock  ·  in use — an Evlat answers

It says	Means
`in use — an Evlat answers`	Evlat is running and listening.
`free — nothing is listening`	Evlat is closed. Open it.
`in use — no answer within 1 s`	Something holds the socket but doesn’t reply in time.
`in use — did not answer (…)`	Something holds the socket and the request failed; the reason is in brackets.
`in use — answered …`	Something that isn’t Evlat answers there.
`none (…)`	There is no socket to use: `EVLAT_SOCKET` isn’t an absolute path, or the path is too long for a socket. See environment.

The signal: line

It says	Means
`ok`	Rows will show.
`not running`	Evlat is closed. Open it.
`no /signal route (404)`	Something older than this Evlat answers on the socket.
`answered <code>`	The socket answered with another status. The HTTP API lists them.
`did not answer (…)`	The socket is held but nothing replied in time, or the request failed; the reason is in brackets.

evlat --capture

evlat --capture [SECONDS]

For debugging hooks. With Evlat quit, it holds the socket itself for 30 seconds, or SECONDS, and prints each event that arrives. Signals show their id, state, ttl and sender; labels and details are never printed.

On a server

The command on a remote server answers evlat --list in one line. See Remote servers.