TZUTC: -0500   
   MSGID: 56425.sync_sys@1:103/705 2b641cbc   
   REPLY: 56414.sync_sys@1:103/705 2b63c945   
   PID: Synchronet 3.20a-Linux master/bcc17e369 Sep 20 202 GCC 11.4.0   
   TID: SBBSecho 3.20-Linux master/f4a2249b0 Sep 21 2024 13:08 GCC 12.2.0   
   BBSID: EOTLBBS   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Re: Out of sync Events   
     By: kk4qbn to nelgin on Wed Oct 02 2024 17:00:44   
      
    > Nope, It's set to no, would'nt that just force everyone off to run the event   
    > though if it was set to yes??   
      
   Possibly, unless the sysop is on, I think it gives you like an hour and a half.   
      
   Aug  4 06:32:50 bbs synchronet: evnt MSGMAINT Waiting for node 1 (status=3)   
   Aug  4 06:33:00 bbs synchronet: evnt MSGMAINT Waiting for node 1 (status=3)   
   Aug  4 06:33:10 bbs synchronet: evnt MSGMAINT Waiting for node 1 (status=3)   
   Aug  4 06:33:10 bbs synchronet: evnt MSGMAINT !TIRED of waiting for node 1 to   
   become inactive (status=3), closing socket 27   
      
      
   But you'd also know about it. I'm not sure if that value is configurable or   
   not. It was just a thought.   
      
   You do have your set to log users off. What if you turn of that off for   
   testing?   
      
   ---   
    þ Synchronet þ End Of The Line BBS - endofthelinebbs.com   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 90/1 102/401 103/1 17 705 105/81 106/201 124/5016   
   SEEN-BY: 153/7715 214/22 218/0 1 215 601 700 720 840 860 870 880 930   
   SEEN-BY: 226/30 227/114 229/110 114 206 317 400 426 428 470 550 700   
   SEEN-BY: 229/705 266/512 280/464 282/1038 291/111 301/1 320/219 322/757   
   SEEN-BY: 342/200 396/45 460/58 633/280 712/848 5075/35   
   PATH: 103/705 218/700 229/426