You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lab admins running shared boards have no independent record of what
is happening on the serial console. The per-client --logfile option
captures output for the user who set it, but the lab owner has no way
to see traffic across all sessions, which hampers post-mortem when a
board ends up in a bad state and the question is which commands got
it there.
Add support for centralised serial-traffic logging on the exporter
host. When LG_SERIAL_TRACE_DIR is set, the exporter passes ser2net's
trace-both option for each acquire, capturing every byte that flows
in either direction to a per-board, per-user file under that directory.
ser2net is started fresh on each resource acquire and stopped
on release, so each instance can include both the board (group
name) and the acquiring user in the filename: <board>-<user>.log
(e.g. bbb-okaro_sjg.log). Repeated acquires by the same user on the
same board append to the same file.
The user identity comes from the coordinator via the new 'user' field
in ExporterSetAcquiredRequest (added in a previous commit). The group
name is plumbed from the resource config through add_resource() into
the ResourceExport so the trace path can use the human-readable board
name instead of the device path.
trace-both-timestamp is enabled so each line is timestamped, which
makes correlating with other audit logs straightforward.
Signed-off-by: Simon Glass <sjg@chromium.org>
Co-developed-by: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments