MSGID: 1:317/3 2a380b7a   
   TZUTC: -0700   
   TID: hpt/lnx 1.9.0-cur 2019-01-08   
   Hi g00r00,   
      
   This may be a stupid question, but I've seen a few times now, where I'll be   
   working on an MPL, and I'll get files that are renamed as filena   
   e[conflicted].ext.   
      
   I'm currently working on updating a MPL from a few years ago, and it keeps it   
   own log file. The log file is now getting renamed to 'conflicted'.    
      
   I'm guessing this is caused by some attempt to write to an file that's   
   unopened? Is this a general 'catch-all' type of event that happens when there   
   is an error somewhere? It would just give me somewhere to start looking for   
   the problem. :)   
      
   In the past, I've seen this with the .mpx files, and also with the chat#.dat   
   files.   
      
   Any clarity you can provide would be greatly appreciated.   
      
   Thanks,   
      
      
   ---   
      
   Black Panther(RCS)   
   aka Dan Richter   
   Castle Rock BBS   
   telnet://bbs.castlerockbbs.com   
   http://www.castlerockbbs.com   
   http://github.com/DRPanther   
   The sparrows are flying again...   
      
   ... Confucius say: "Its stuffy inside fortune cookie"   
      
   --- Mystic BBS v1.12 A47 2021/09/07 (Linux/64)   
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (1:317/3)   
   SEEN-BY: 1/123 90/1 105/81 114/705 120/340 123/120 131 129/305 226/30   
   SEEN-BY: 227/114 229/101 424 426 428 452 550 664 700 240/5832 249/206   
   SEEN-BY: 249/307 317 400 282/1038 292/854 298/25 301/1 305/3 317/3   
   SEEN-BY: 322/757 342/200 633/280   
   PATH: 317/3 229/426