From rswindell@VERT to CVS commit on Sat Aug 8 12:24:27 2020
src/sbbs3/scfg scfgnode.c 1.36 1.37
Update of /cvsroot/sbbs/src/sbbs3/scfg
In directory cvs:/tmp/cvs-serv25400
Modified Files:
scfgnode.c
Log Message:
The problem: the sysop (me) is not notified of critical errors (e.g. synchro.net zone file problems) in a timely manner.
Part of the solution: notify a configured user (e.g. user #1) via short-message/telegram and email/netmail logged-errors when messages of a configured severity (e.g. "Critical") are logged.
The second part of the solution (coming next) will be allowing timed events to log a message of a configurable severity logged when the event fails (returns a non-zero error level to sbbs).
I'm saving the error-notification-user-number and log-severity as part of the node.cnf file because:
- that's where the validation user number is already set
- I can conceive of a large system were certain node ranges (different instances of sbbs) might want different operators to be notified of logged-errors
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
From Rob Swindell@VERT to Git commit to sbbs/master on Sun Sep 6 11:01:40 2020