On 2019 Jan 05 05:33:00, you wrote to me:   
      
    >> i don't know how bbbs logs or if you are on *nix but i have increased my   
    >> syslo retention so i could have time to go back and hunt down anomalies   
    >> days or week later...   
      
    AI> I am running slackware and I haven't deleted any logs yet (it's a new   
    AI> install). I will add the logs to logrotate at some point. I usually keep   
   30   
    AI> days of logs.   
      
   on our ubuntu servers, our (non-bbbs) setup logs to syslog and that's where we   
   have to monitor/grep to see what the main part of the bbs is doing... some   
   additional parts log to their own log files outside of syslog but not many...   
      
    AI> BBBS writes classic logs. Mailer sessions are logged in each nodes log   
    AI> and utilities like bogus (the tosser/scanner) log to log0.   
      
   ahhh... ok, so it doesn't use the logging facility on the system? i know that   
   there is a way for it to write to individual logs but i rarely ever change it   
   to do that...   
      
    >> tldr; do the logs indicate why that file was left behind and the   
    >> processing didn't complete properly?   
      
    AI> No, the log0 just logs one line like this..   
      
    AI> 181231 21:15 Message base locked   
      
   ahhh... and there's nothing further back indicating an abort or exiting error   
   condition?   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
   Do you manage your own servers? If you are not running an IDS/IPS yer doin' it   
   wrong...   
   ... Clear out, or I'll set the cats on you   
   ---   
    * Origin:  (1:3634/12.73)