Subj : mis.log
To   : g00r00
From : Michael Pierce
Date : Wed Jun 24 2020 07:58 pm

 gr> I don't think its dying it just doesn't write to the log until it gets
 gr> enough data to write to the log, thats what caching is.  So if you
 gr> either want it to write in chunks of logs at a time, or you want it to
 gr> write line by line.

well it stops writing, but the mis server window keeps writing ie last time I caught it, there was more than 2 hours time difference between what was written to mis.log and what was on the mis server screen (running as a detached screen)

poll.log does not have this problem.

 gr> Maybe what I can do for MIS is have it update the log after a number
 gr> of seconds even if the cache isn't filled yet.
one thing I have noticed, is when it happens, it will only write the date

here is the last few lines of mis from the last time it happened

+ 2020.06.24 19:50:54  BINKP > Connect on slot 1/5 (73.11.56.74)
+ 2020.06.24 19:50:54  BINKP 1-HostName c-73-11-56-74.hsd1.or.comcast.net
+ 2020.06.24 19:50:54  BINKP 1-Country  United States of America (US)
+ 2020.06.24 19:50:54  BINKP 1-System fluxcap.dynv6.net
+ 2020.06.24 19:50:54  BINKP 1-SysOp Michael Pierce
+ 2020.06.24 19:50:54  BINKP 1-Location Portland, Or
+ 2020.06.24 19:50:54  BINKP 1-Mailer binkd/1.1a-96/Linux binkp/1.1
+ 2020.06.24 19:50:54  BINKP 1-Queued 0 files for 1:340/201.2@fidonet
+ 2020.06.24 19:50:54  BINKP 1-Queued 0 files for 21:2/145.2@fsxnet
+ 2020.06.24



Michael

.... Cap'n, I threw your stinkin palm tree overboard!
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

.