Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,658 of 16,010    |
|    Bj”rn Wiberg to g00r00    |
|    Default events    |
|    03 Aug 21 11:24:27    |
      TID: Mystic BBS 1.12 A47       MSGID: 2:201/137 d6fe2773       TZUTC: 0200       Hello g00r00!              I just noticed that some of the default events in A47 could use some small       adjustments:              * The "Poll echomail" event should use "mis poll" instead of "fidopoll".              * The "Poll echomail" event should probably have at least "Semaphore:       !mutil.bsy" to avoid colliding with other invocations of mutil, if any. Or       perhaps, even better, "Semaphore: !(poll.bsy|mutil.bsy)" to also avoid       colliding with any other polls of other events (e.g. the "Send outbound       echomail" event).              * The "Send outbound echomail" should probably have "Semaphore:        (mutil.bsy|poll.bsy)" to avoid colliding with any other invocations of mutil       and mis poll.              * The "Send Hatched Files" should probably have "Semaphore: file       one.out!mutil.bsy" to avoid colliding with any other invocations of mutil.              * The "Toss incoming echomail" probably does not need "|netmail.in" in       Semaphore and Kill After. I couldn't find any references to netmail.in in       neither mutil or mis, so perhaps it is safe to remove those?              * The "Weekly maintanence" event has a small typo in it; should probably be       "Weekly maintenance". :)              And, some "closing thoughts":              * Ideally, all invocations of mis or mutil on Linux should have ./ at the       beginning of their paths, as the events are executed with the Mystic base       directory as the current working directory, and . is seldom in a user's PATH.              * The "Weekly maintanence" event should ideally have "Semaphore: !mutil.bsy"       to avoid colliding with other invocations of mutil, if this were possible for       Shell events, which it is not? That possibility would be nice to have.       Although then one would have to think of what should be done if the semaphore       exists -- should the event be skipped or postponed? On my system, I have added       a check for this to the Shell line instead:       if [ ! -e /home/bbs/mystic/semaphore/mutil.bsy ]; then ./mutil maint.ini; fi       ...with the downside of having to specify the path to the semaphore.              Your thoughts on all this are welcome. :)              Best regards       Bj”rn       --- Mystic BBS v1.12 A47 2021/07/31 (Linux/64)        * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)       SEEN-BY: 1/123 30/0 80/1 90/1 103/705 105/81 120/340 123/131 124/5016       SEEN-BY: 129/305 154/10 201/0 137 203/0 124 218/700 221/0 1 6 226/30       SEEN-BY: 227/114 702 229/101 424 426 428 452 550 700 981 1016 1017       SEEN-BY: 230/0 240/1120 5832 249/206 307 317 400 261/38 280/464 5003       SEEN-BY: 282/464 1038 292/854 8125 301/0 1 101 113 317/3 320/219 322/757       SEEN-BY: 335/364 341/66 342/200 396/45 633/280 712/848 920/1 2452/250       SEEN-BY: 3634/24 5020/1042 5058/104       PATH: 201/137 0 203/0 280/464 301/1 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca