What problem does it solve?
Sysops and developers working with Synchronet BBS often waste time searching the wrong log files when troubleshooting issues, as log locations vary drastically based on operating system, daemon mode, init system, and whether multiple BBS instances share storage. This Skill eliminates that guesswork by providing a complete map of all possible log sources and the conditions that determine where each log line is written.
Core Features & Use Cases
- Cross-platform log mapping: Covers Windows (sbbsctrl, NT Services, console) and *nix (syslog, journalctl, interactive stdout) log sources, including per-category data files like hack.log, error.log, and HTTP access logs.
- Edge case handling: Addresses common traps like multi-instance shared text directories causing cross-BBS ip.can entries, Windows-specific sbbsctrl log files appearing on *nix systems, and post-rotation empty log files.
- Use Case: If you are investigating a web rate-limit block or a failed login attempt, this Skill tells you exactly which log source to check first, how to tail it live, and how to cross-reference related entries like ip.can filters.
Quick Start
Use the logs skill to identify the correct log source to investigate a recent web rate-limit block on your Synchronet BBS.