• src/sbbs3/logfile.cpp

    From rswindell@1:103/705 to CVS commit on Fri Apr 13 16:59:06 2018
    src/sbbs3 logfile.cpp 1.60 1.61
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv26751

    Modified Files:
    logfile.cpp
    Log Message:
    errormsg() logs the "useron", when applicable, even for timed events (e.g.
    REP unpacking).

    --- SBBSecho 3.04-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Thu Oct 25 19:15:09 2018
    src/sbbs3 logfile.cpp 1.62 1.63
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv11622

    Modified Files:
    logfile.cpp
    Log Message:
    Now that sbbs_t::lputs() adds the <useron alias>, adding it here (useron=x)
    to the log message becomes redundant.

    --- SBBSecho 3.06-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Fri Jan 4 14:15:13 2019
    src/sbbs3 logfile.cpp 1.64 1.65
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv19104

    Modified Files:
    logfile.cpp
    Log Message:
    Partially revert the change in rev 1.63: eprintf() does not log the
    <useron alias>, so we need to include it in the log message here if we
    want the current user's alias included in event related log messages
    (e.g. unpacking QWK-REP packages).


    --- SBBSecho 3.06-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Sun Jun 23 13:12:04 2019
    src/sbbs3 logfile.cpp 1.65 1.66
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv25331

    Modified Files:
    logfile.cpp
    Log Message:
    Use ctime_r() for the error.log timestamp string rather thean timestr() -
    this insures:
    1. the timestamp always includes the seconds
    2. the tiemstamp is always in 24-hour format (no am/pm indication)

    For systems that are configured (in SCFG) for "Military" (24 hour) time format, the error.log timestamps should appear the same as before.


    --- SBBSecho 3.07-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Sat Aug 8 12:32:30 2020
    src/sbbs3 logfile.cpp 1.68 1.69
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv30030

    Modified Files:
    logfile.cpp
    Log Message:
    *lower* log-levels are more severe.

    --- 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 Dec 20 17:11:56 2020
    https://gitlab.synchro.net/main/sbbs/-/commit/48f73ca167262efb1a09078f
    Modified Files:
    src/sbbs3/logfile.cpp
    Log Message:
    Don't log errno info for ERR_CHK errormsg() callsThe errno (global error number) information is not relevant for any sbbs "checking" type errors.Also, use safe_strerror() for thread-safe errno descriptions.
    --- 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 May 16 16:47:09 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/3d1e05e5015a0872a2a72fb7
    Modified Files:
    src/sbbs3/logfile.cpp
    Log Message:
    Log the current Git branch and hash along with every errorThis eliminates any ambiguity about what exact version was in use when each error is logged.
    --- SBBSecho 3.14-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 Thu Dec 29 14:16:20 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/4908a3883646356c357f6814
    Modified Files:
    src/sbbs3/logfile.cpp
    Log Message:
    Resolve warning: ISO C++ forbids converting a string constant to ΓÇÿchar*ΓÇÖ --- SBBSecho 3.20-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 Mon Jan 30 16:00:04 2023
    https://gitlab.synchro.net/main/sbbs/-/commit/d99905a420dd2f394c5dce69
    Modified Files:
    src/sbbs3/logfile.cpp
    Log Message:
    Lowercase the topics in hack and spam action messages
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell (on Windows 11)@1:103/705 to Git commit to main/sbbs/master on Sun Feb 25 18:06:16 2024
    https://gitlab.synchro.net/main/sbbs/-/commit/62852439c523e1d09e6b10b1
    Modified Files:
    src/sbbs3/logfile.cpp
    Log Message:
    Don't log errno value and description as part of ERROR log msg, when 0

    If errno is 0, it's definitely no proividing anything of value here. Of
    course, sometimes errno might be non-zero and still be unrelated to the error message. <shrug>

    For Nelgin:
    !ERROR 0 (Success) in exec.cpp line 644 (js_execfile) compiling "something.js" access=0
    <nelgin> I don't quite get why a successful execution is logged as an error
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)