> Synchronet has a lot of per-user configuration options for how QWK packets are
> reated. I would try experimenting with them.

I received an email this am from a user complaining about how the board was
acting and mentioned the time change.  I thought they were mistaken.

I tried logging on just now to give Marty a little guidance on how to
"work" the QWK configuration settings.  I received a "sorry time reduced...
goodbye" result for a system event that is allegedly scheduled for 05:00.

Local time is now after 09:30 and I have confirmed that the OS time (linux) is
correct.

The 05:00 event appears to be MSGMAINT.  I just kicked it off manually and
that fixed it.  That was after I tried restarting Synchronet and getting
the same (not good) results.

I have never had Synchronet mess itself over the time change before.
It is with 3.20 that I upgraded to just over a week ago.


 * SLMR 2.1a * Ted Kennedy's Bumper Sticker: My other car is underwater.
---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP