Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_SYSOPS    |    Synchronet Multinode BBS Software Suppor    |    33,243 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 30,451 of 33,243    |
|    kk4qbn to Digital Man    |
|    Out of sync Events    |
|    03 Oct 24 20:49:28    |
      TZUTC: -0400       MSGID: 56442.sync_sys@1:103/705 2b6555af       REPLY: 56435.sync_sys@1:103/705 2b653874       PID: Synchronet 3.20a-Linux master/51108b220 Oct 01 202 GCC 14.2.1       TID: SBBSecho 3.20-Linux master/f4a2249b0 Sep 21 2024 13:08 GCC 12.2.0       BBSID: KK4QBN       CHRS: UTF-8 4       > Re: Out of sync Events       > By: kk4qbn to Digital Man on Thu Oct 03 2024 07:40 am              > If it ran at 0145 instead of 0100, that would be *late* not early. Why would       > it? Because another event was running possibly.              It did'nt run at 0145, it ran at 2145, the day before.              at 945pm on 10/1 the event ran and it showed 10/2 as the date. on the terminal       service window. it does'nt show the date change on the copilot formatted logs       though.       But this is how the terminal services window looked when it ran other then       scrolling from up to down instead of down/up              10/01 9:46 PM srvc 0219 ActiveUser-UDP [40.136.248.88] Hostname:       h88.248.136.40.dynamic.ip.windstream.net       10/01 9:46 PM srvc 0219 ActiveUser-UDP [40.136.248.88] Connection accepted on       192.168.1.5 port 11 from port 54194       10/02 9:45 PM evnt DOORMAINT Running 16-bit DOS timed event: DOORMAINT        10/01 9:45 PM srvc 0218 ActiveUser-UDP [40.136.248.88] JavaScript service       thread terminated (1 clients remain, 21 total, 945 served)       10/01 9:45 PM srvc 0218 ActiveUser-UDP [40.136.248.88] Hostname:       h88.248.136.40.dynamic.ip.windstream.net                     > I'm not sure what you're referring to here.              I'm afraid now that it is logging through syslog I cannot get the log formatted       like it was on the terminal service.. either way it appeared as if it was       running a future event instead of running it late, that is what I was referring       to. it really does'nt matter, It just looked off to me, probably operator       error.. some way..              ---        ■ Synchronet ■ KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 153/757 7715 154/10       SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206       SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512       SEEN-BY: 280/464 5003 5006 282/1038 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: 467/888 633/280 712/848 770/1 5020/400 5054/30 5075/35       PATH: 103/705 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca