TZUTC: -0800   
   MSGID: 54277.syncprog@1:103/705 2de1287e   
   PID: Synchronet 3.21b-Linux master/5c73d262c Jan 21 2026 GCC 12.2.0   
   TID: SBBSecho 3.35-Linux master/0958ba161 Jan 25 2026 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/a6dd4c68cdba571f7712e1a1   
   Modified Files:   
   	src/sbbs3/nopen.c   
   Log Message:   
   A little paranoia around comparing a file date/time against current date/time   
      
   The file could be timestamped in the future (especially on a network FS).   
   We could maybe have been considering the lock too old (e.g. for REP packet   
   unpacking) in this case and explain some of the collisions I see between   
   even threads on different machines unpacking the same REP Packet (or trying   
   to), leading to errors like this one:   
     !ERROR 16 (Device or resource busy) renaming /sbbs/data/file/0290.rep   
     (20480 bytes) to /sbbs/data/file/0290.rep.697b1a12.bad   
      
   This shouldn't be possible if the mutex files are working as designed.   
   --- SBBSecho 3.35-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715   
   SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/134 206 317 400 426 428 470 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426