logs

The one place the server's logging is configured.

Every Selkies module logs through a short logger name that says which part of the server spoke (main, server, ws, webrtc, signaling, display, input, gamepad, audio, printing, webcam, stats, audit), rendered as LEVEL:name:message like pixelflux's own bracketed [X11]/[Wayland] lines beside them. INFO is the story of a session as an operator reads it back from a user: the settings the server came up with, what a client connected as, the capture and encoder path each display took, and every later change or failure; the mechanics behind those events (each reconfiguration step, each broadcast, each task) are DEBUG. Debug mode (--debug) opens DEBUG on every Selkies logger, and the same flag reaches pixelflux as debug_logging.

Two sources would bury a debug run on their own and are held back even then. Pillow logs every PNG chunk it writes at DEBUG, and the cursor path encodes a PNG per cursor change, so the PIL logger is pinned at WARNING. The vendored WebRTC and ICE stacks log every STUN check, DTLS record and state change; PacedFilter on the root handler lets the first record of each message template through and then one per PACE_PERIOD_S seconds, carrying the count of the records it held back, while the per-packet RTP and SCTP loggers stay at INFO outright.