Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 26:39:46 |
Calls: | 286 |
Calls today: | 1 |
Files: | 899 |
Messages: | 76,579 |
Howdy,
I've been trying to get IMAP into Debug mode (for my delete issue on mac), and it wont go into debug mode unless I put LogLevel = Debug in sbbs.ini
In services.ini I have this:
[IMAP]
Enabled=true
Port=143
Command=imapservice.js
Options=NO_HOST_LOOKUP|NO_USER_PROT
LogLevel=Debug
(I even tried lowercase "debug"). That should do it right? IE: Only IMAP in verbose debug mode, and everything else (via sbbs.ini) in Informational.
I've been trying to get IMAP into Debug mode (for my delete issue on mac), and it wont go into debug mode unless I put LogLevel = Debug in sbbs.ini
In services.ini I have this:
[IMAP]
LogLevel=Debug
Yeah, that tracks (sounds correct).
Re: per-service log levels
By: Digital Man to deon on Wed Jan 22 2025 04:21 pm
I've been trying to get IMAP into Debug mode (for my delete issue on mac), and it wont go into debug mode unless I put LogLevel = Debug in sbbs.ini
In services.ini I have this:
[IMAP]
LogLevel=Debug
Yeah, that tracks (sounds correct).
Howdy, so I finished my debugging, but I dont think debuglevel is working for services (or it didnt work for me, unless I put sbbs.ini LogLevel = Debug).
Anyway, I have now reverted sbbs.ini back to LogLevel = Informational, and services.ini [IMAP] is still LogLevel = Debug, but its not doing "Debug" logging.
ie: log(LOG_DEBUG,'Im in DEBUG mode'); in imapservice.js doesnt appear in journalctl (changing to LOG_WARNING does though).
In order for *any* debug-level log messages to be logged by sbbs (and that includes all scripts executed by sbbs, including services), you'd have to have one of the LogLevel settings in sbbs.ini set to "debug". Additionally, each service can also be set to filter-out lower-severity log messages (by setting its log level to something less than "debug").