1. Forum
  2. FidoNet Areas
  3. SYNC PROGRAMMING

  • src/sbbs3/scfg/scfgnode.c

    From rswindell@1:103/705 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

    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to sbbs/master on Sun Sep 6 11:01:40 2020
    https://gitlab.synchro.net/sbbs/sbbs/-/commit/c2b64f0228de63cdb70404c6
    Modified Files:
    src/sbbs3/scfg/scfgnode.c
    Log Message:
    Update a lot of help text and fix a couple cosmetic issues.
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Sun Nov 29 00:40:46 2020
    https://gitlab.synchro.net/main/sbbs/-/commit/a3de2a8a6648344623a52b23
    Modified Files:
    src/sbbs3/scfg/scfgnode.c
    Log Message:
    Remove now-obsolete help text about FirstNode config being shared... between all nodes of a instance sbbs instance. That's now no longer true.
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Tue Jan 5 02:09:41 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/b68df653c187127dbdd5f536
    Modified Files:
    src/sbbs3/scfg/scfgnode.c
    Log Message:
    Make default node 2+ directory paths derived from node 1's directoryFor deon's use with Docker:When creating new nodes (after node 1), derive the new node directory from node 1's configured directory if possible (e.g. it has a '1' in it). So if Node 1's directory is /blah/bbsdir1, then node 2's directory will default to /blah/bbsdir2. When creating node 1 (the first node), it still defaults to "../node1".
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Rob Swindell on Thu Jan 7 07:02:06 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/b68df653c187127dbdd5f536 Modified Files:
    src/sbbs3/scfg/scfgnode.c
    Log Message:
    Make default node 2+ directory paths derived from node 1's directory

    For deon's use with Docker:
    When creating new nodes (after node 1), derive the new node directory from node 1's configured directory if possible (e.g. it has a '1' in it). So if Node 1's directory is /blah/bbsdir1, then node 2's directory will default to /blah/bbsdir2. When creating node 1 (the first node), it still defaults to "../node1".

    ;-/


    ~Ephram

    ---
    þ Synchronet þ The Realm of Dispair telnet ephram.synchro.net 2323 ssh 2222 web 82
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)