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,461 of 33,243 |
| kk4qbn to Gamgee |
| Re: Out of sync Events |
| 04 Oct 24 20:01:59 |
TZUTC: -0400 MSGID: 56452.sync_sys@1:103/705 2b66a739 REPLY: 56449.sync_sys@1:103/705 2b65f935 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 COLS: 80 BBSID: KK4QBN CHRS: CP437 2 NOTE: SlyEdit 1.89b (2024-05-11) (ICE style) Re: Re: Out of sync Events By: Gamgee to kk4qbn on Fri Oct 04 2024 07:43:00 kk>> I mean, It really does'nt matter, I just knew I wasn't tripping when it kk>> started running but it was running for 10/2, not 10/1 but it was 0945pm kk>> 10/1 Ga> Could it just be that the BBS machine's time (or TIME ZONE) is set wrong? Ga> Sometimes the easiest answer is the correct one... ;-) That could be a possiblily there is a 4 hour difference there, But it would have had to jump from edt to pdt in a total of a just a couple seconds then jump back because that is how quick it happened.. ghost in the machine or more than likely just user error that I have'nt found yet.. It has been running at 0100 every morning just like it suppose to every morning.. but that one night it just decided that at 2145 the time was 0145 the next day and that it hasnt ran door maint yet, so it ran it, then went back to 2145.. |
(c) 1994, bbs@darkrealms.ca