• MIS POLL

    From pweck@21:3/113 to All on Tue Nov 10 13:49:22 2020
    I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

    any ideas?π

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From HSM@21:2/162 to pweck on Tue Nov 10 15:21:34 2020
    On 10 Nov 2020, pweck said the following...

    I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

    any ideas?π


    I have trouble running any events using Mystic to schedule them. I've since scheduled all my events in chrontab (fcrontab is what I use). Works fine that way.

    -=- Gary aka HSM -=-
    -=Mystic.BBSGameTime.com=-

    --- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
    * Origin: BBS GameTime - mystic.BBSGameTime.com:23 (21:2/162)
  • From Warpslide@21:3/110 to pweck on Tue Nov 10 15:33:00 2020
    On 10 Nov 2020, pweck said the following...

    I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

    I had to change the events to include the full path:

    e.g:
    /home/pi/mystic/mis poll forced

    Then it seemed to work for me.

    Jay

    ... What do you call a dinosaur with one eye? A do-you-think-he-saur-us.

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Avon@21:1/101 to pweck on Wed Nov 11 12:06:34 2020
    On 10 Nov 2020 at 01:49p, pweck pondered and said...

    I noticed that my events are not running, specifically for the ./mis poll

    do you run something like

    ./mis poll 21:1/100

    if it's just ./mis poll then that's not enough.

    events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

    the fact that this line ran OK makes me wonder if you had not specified a
    node to poll?

    I usually set up events to poll a HUB from Agency BBS and just put the HUB address in the line e.g. ./mis poll 21:1/100

    I tend to stay clear of the 'forced' switch as I like the idea of more
    granular control over which echomail node(s) I want to poll and when.

    Using 'forced' will force a poll to all echomail nodes regardless of if there is mail at your end to send etc. or not.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to HSM on Wed Nov 11 12:08:05 2020
    On 10 Nov 2020 at 03:21p, HSM pondered and said...

    I have trouble running any events using Mystic to schedule them. I've since scheduled all my events in chrontab (fcrontab is what I use).
    Works fine that way.
    --- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)

    It's probably a pathing issue often using ./mis poll [address] works well for me... the error code mystic returns will also help you debug if ever
    interested in looking into it again :) The result code should be 0 if it's
    127 or similar then it's more likely the path issue I refer to.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to pweck on Tue Nov 10 15:57:42 2020
    Re: MIS POLL
    By: pweck to All on Tue Nov 10 2020 01:49 pm

    I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

    I noticed that too a version or three ago.

    It looks like you are running the prealpha so I'd recommend updating to the latest prealpha release and see if that makes a difference.

    Ttyl :-),
    Al

    ... When I am right nobody remembers - When I am wrong nobody forgets!
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From paulie420@21:2/150 to Avon on Tue Nov 10 17:23:19 2020
    do you run something like
    ./mis poll 21:1/100

    if it's just ./mis poll then that's not enough.

    Is this a fact? I believe I only run ./mis poll... I haven't NOTICED not getting any network activity - but....

    What should I change it to? ./mis forced??

    Ugh - I wanna make sure I'm getting everything.
    Seems to work under Linun @ ./mis poll...



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Al@21:4/106.1 to paulie420 on Tue Nov 10 19:49:31 2020
    Re: Re: MIS POLL
    By: paulie420 to Avon on Tue Nov 10 2020 05:23 pm

    Is this a fact? I believe I only run ./mis poll... I haven't NOTICED not getting any network activity - but....

    What should I change it to? ./mis forced??

    I use ./mis poll send

    That will send out whatever is waiting in the outbound.

    Ttyl :-),
    Al

    ... I couldn't repair the brakes.. So I made your horn louder!
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From pweck@21:3/113 to Warpslide on Tue Nov 10 21:22:50 2020
    I noticed that my events are not running, specifically for the ./mis events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

    I had to change the events to include the full path:

    e.g:
    /home/pi/mystic/mis poll forced

    Then it seemed to work for me.


    Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced
    correct?

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to Avon on Tue Nov 10 21:28:46 2020
    I noticed that my events are not running, specifically for the ./mis

    do you run something like

    ./mis poll 21:1/100
    Yes. That is how it is in events and tested command line as well.Since I forced it on a command line this afternoon, it did not run. As well it seems I had to run ./mutil mailin too....

    Av> if it's just ./mis poll then
    that's not enough. Av>
    events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

    the fact that this line ran OK makes me wonder if you had not specified a node to poll?

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to Avon on Tue Nov 10 21:30:07 2020
    It's probably a pathing issue often using ./mis poll [address] works
    well forme... the error code mystic returns will also help you debug if everinterested in looking into it again :) The result code should be 0
    if it's127 or similar then it's more likely the path issue I refer to.

    Where would I see the error code? Thanks

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to HSM on Tue Nov 10 21:31:29 2020
    I noticed that my events are not running, specifically for the ./mis events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

    any ideas?π


    I have trouble running any events using Mystic to schedule them. I've sincescheduled all my events in chrontab (fcrontab is what I use).
    Works fine thatway.


    Ya my .nix skills are lacking so far to do that. More reading...lol

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to Al on Tue Nov 10 22:54:42 2020
    I noticed that too a version or three ago.

    It looks like you are running the prealpha so I'd recommend updating to thelatest prealpha release and see if that makes a difference.

    thanks, yes i have the latest release. maybe i need to re-install...ugh

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From Al@21:4/106.1 to pweck on Tue Nov 10 21:46:18 2020
    Re: Re: MIS POLL
    By: pweck to Al on Tue Nov 10 2020 10:54 pm

    thanks, yes i have the latest release. maybe i need to re-install...ugh

    Yeah, in the case of the prealphas it's a good idea to keep up to date with what g00r00 is up to. I see there is a newer one (11/06) that I have to catch up with too.

    Ttyl :-),
    Al

    ... You can name your salary here, I call mine fred.
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to paulie420 on Wed Nov 11 19:11:37 2020
    On 10 Nov 2020 at 05:23p, paulie420 pondered and said...

    do you run something like
    ./mis poll 21:1/100

    if it's just ./mis poll then that's not enough.

    Is this a fact? I believe I only run ./mis poll... I haven't NOTICED not getting any network activity - but....

    I'm running the current public release, if you type mis poll you get

    POLL SEND - Only send/poll if node has new outbound messages
    POLL FORCED [Type] - Poll/send to all nodes of session [Type] (Blank/All)
    POLL [Address] - Poll/send echomail node [Address] (ex: 46:1/100)

    So I suggest use the last option in your shell line and plug in an address to poll.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Wed Nov 11 19:12:07 2020
    On 10 Nov 2020 at 07:49p, Al pondered and said...

    I use ./mis poll send

    That will send out whatever is waiting in the outbound.

    This is the shell line I use when running mailout.ini

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to pweck on Wed Nov 11 19:13:51 2020
    On 10 Nov 2020 at 09:28p, pweck pondered and said...

    ./mis poll 21:1/100
    Yes. That is how it is in events and tested command line as
    well.Since I forced it on a command line this afternoon, it did not
    run. As well it seems I had to run ./mutil mailin too....

    So ./mis poll 21:1/100 from the command line did not poll the node?

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)

    Have you compiled your nodelist?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Wed Nov 11 19:14:52 2020
    On 10 Nov 2020 at 09:46p, Al pondered and said...

    Yeah, in the case of the prealphas it's a good idea to keep up to date with what g00r00 is up to. I see there is a newer one (11/06) that I
    have to catch up with too.

    :) Have fun with that.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Tue Nov 10 22:36:11 2020
    Re: Re: MIS POLL
    By: Avon to Al on Wed Nov 11 2020 07:14 pm

    Yeah, in the case of the prealphas it's a good idea to keep up to
    date with what g00r00 is up to. I see there is a newer one (11/06)
    that I have to catch up with too.

    :) Have fun with that.

    It's actually quite mellow these days.. one or two updates a week. I remember a time when there was one or two a day!

    Ttyl :-),
    Al

    ... Help! I've fallen and can't reach my beer!
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to Al on Wed Nov 11 19:59:56 2020
    On 10 Nov 2020 at 10:36p, Al pondered and said...

    It's actually quite mellow these days.. one or two updates a week. I remember a time when there was one or two a day!

    Great software, does cool things. That said, after the events of the year the fun of it has rather left the building for me. I just don't get as in to it as much as I once did because of this. Nuff said.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Warpslide@21:3/110 to pweck on Wed Nov 11 09:12:17 2020
    On 10 Nov 2020, pweck said the following...

    Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced
    correct?

    No, you only include the period if you're executing from the current
    directory.

    So if mis was located in /home/pi/mystic you could execute it with ./mis provided you were in that directory. Or from anywhere else you provide the full path /home/pi/mystic/mis

    I'm running on a Raspberry Pi, here is how I have my two events setup:

    Active │ Yes
    Description │ Toss incoming echomail
    Event Type │ Semaphore
    Exec Hour │ 0
    Exec Min │ 0
    Shell │ /home/pi/mystic/mutil mailin.ini
    Semaphore │ echomail.in|netmail.in
    Kill After │ echomail.in|netmail.in


    Active │ Yes
    Description │ Poll echomail
    Event Type │ Interval
    Exec Hour │ 1
    Exec Min │ 0
    Shell │ /home/pi/mystic/mis poll forced|/home/pi/mystic/mutil mailin.ini
    Semaphore │
    Kill After │

    Hope this helps.

    Jay

    ... The male pig puts everyone to sleep. You might say he's quite a boar.

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From pweck@21:3/113 to Avon on Wed Nov 11 08:49:45 2020
    Yes. That is how it is in events and tested command line as well.Since I forced it on a command line this afternoon, it did not run. As well it seems I had to run ./mutil mailin too....

    So ./mis poll 21:1/100 from the command line did not poll the node?
    yes it works when I manually run it from a command prompt. automated seems hit and miss

    Have you compiled your nodelist?
    i have an event that compiles it daily (merge_node.ini) but looking at logs, it has not been running...<sigh>

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to Avon on Wed Nov 11 08:50:57 2020
    Yeah, in the case of the prealphas it's a good idea to keep up to dat with what g00r00 is up to. I see there is a newer one (11/06) that I have to catch up with too.

    thanks, yes it appears I am behind now too...

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to Warpslide on Wed Nov 11 08:59:10 2020
    ./home/pi/mystic/mis poll forced
    correct?

    No, you only include the period if you're executing from the current directory.

    Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

    Wa>
    So if mis was located in /home/pi/mystic you could execute it with ./mis provided you were in that directory. Or from anywhere else you provide thefull path /home/pi/mystic/mis
    thanks, I will remove the period and try again


    I'm running on a Raspberry Pi, here is how I have my two events setup:

    Active │ Yes
    Description │ Toss incoming echomail
    Event Type │ Semaphore
    Exec Hour │ 0
    Exec Min │ 0
    Shell │ /home/pi/mystic/mutil mailin.ini
    Semaphore │ echomail.in|netmail.in
    Kill After │ echomail.in|netmail.in


    Active │ Yes
    Description │ Poll echomail
    Event Type │ Interval
    Exec Hour │ 1
    Exec Min │ 0
    Shell │ /home/pi/mystic/mis poll forced|/home/pi/mystic/mutil mailin.ini Semaphore │
    Kill After │
    Thank you!

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From ryan@21:1/168 to pweck on Wed Nov 11 09:22:15 2020
    Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

    Not a problem, you just need to spell out the absolute path like

    "/mystic/mis poll force" or whatever the syntax is.

    --- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Warpslide@21:3/110 to pweck on Wed Nov 11 12:29:47 2020
    On 11 Nov 2020, pweck said the following...

    Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

    Yup, if you have mystic installed in /mystic, you'd just update the full path to be /mystic/mis poll forced or /mystic/mis poll send, whatever the case may be.

    Jay

    ... I'm positive I just lost an electron. Better keep an ion that.

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From pweck@21:3/113 to Warpslide on Wed Nov 11 18:47:25 2020
    Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

    Yup, if you have mystic installed in /mystic, you'd just update the full pathto be /mystic/mis poll forced or /mystic/mis poll send, whatever the case maybe.


    Thanks I figured. Ok, will try and see if it solves the problems..

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From paulie420@21:2/150 to Al on Wed Nov 11 17:57:15 2020
    Is this a fact? I believe I only run ./mis poll... I haven't NOTICED getting any network activity - but....

    I use ./mis poll send
    That will send out whatever is waiting in the outbound.
    Ttyl :-),
    Al

    You know, when I posted this it was more for the wondery of if I needed full paths or not; I actually do run ./mis send, too... and ./mis poll for another event...

    If I were a betting man, I think I'd say that under Linux, you can still just call it with ./ ... that is basically 'a full path' as long as mis runs in /mystic...

    I think for the Windows users maybe they are the ones that need to modify the commands when upgrading to a47... (With full pathnames; I know we all have to modify to mis...)



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to pweck on Wed Nov 11 17:58:07 2020
    Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced

    /home/pi/mystic/./mis poll



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to pweck on Wed Nov 11 17:58:57 2020
    On 10 Nov 2020, pweck said the following...

    It's probably a pathing issue often using ./mis poll [address] works well forme... the error code mystic returns will also help you debug everinterested in looking into it again :) The result code should be if it's127 or similar then it's more likely the path issue I refer to

    Where would I see the error code? Thanks

    In your mis WFC screen, go to events and if theres a '0' next to them there was no errors on the last run.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Al on Wed Nov 11 18:01:05 2020
    Re: Re: MIS POLL
    By: pweck to Al on Tue Nov 10 2020 10:54 pm

    thanks, yes i have the latest release. maybe i need to re-install...u

    Yeah, in the case of the prealphas it's a good idea to keep up to date withwhat g00r00 is up to. I see there is a newer one (11/06) that I have to catchup with too.

    Ttyl :-),
    Al

    Hey Al, thanks for posting this... I upgraded to a47 - are you stating that he continues to modify the a47 prealpha and a sysOp would be best served by updating the update every couple week?

    I'm familiar with how Synchronet does it - and you just pull the github and get a newer build... but I was under the impression that I just upgrade to a47 and thats THE prealpha release.

    Are you stating that he continues to modify that a47 build and I should check back to make sure I'm on the newest date??



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Avon on Wed Nov 11 18:02:28 2020
    I'm running the current public release, if you type mis poll you get

    POLL SEND - Only send/poll if node has new outbound messages POLL FORCED [Type] - Poll/send to all nodes of session [Type] (Blank/All)POLL [Address] - Poll/send echomail node [Address] (ex: 46:1/100)

    So I suggest use the last option in your shell line and plug in an
    address topoll.

    Ok - I'm running the most current release too - am I correct in thinking that I should use my hub, as that address ... to poll?



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Avon on Wed Nov 11 18:04:21 2020
    Have you compiled your nodelist?

    Sorry for all the questions - but, is 'compiling your nodelist' running my mergenodelist.ini ??

    I always add the newest nodelists to my /mystic/nodelists directory... and I run ./mutil mergonodelists.ini - which... merges all those nodelists. Are my nodelists 'compiled'???



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Avon on Wed Nov 11 18:08:11 2020
    Great software, does cool things. That said, after the events of the
    year thefun of it has rather left the building for me. I just don't get
    as in to it asmuch as I once did because of this. Nuff said.


    Not starting any drama or debate; but this statement, by you, is really a downer for... me. Just hope that you know that PLENTY of folks in this BBS community both appreciate, count on and know what YOU do for this scene.

    I can understand the reasoning, and wish that you received the appreciation that you so duly DESERVE.

    I'd be much happier to hear that you love this hobby and all the moving parts within it- I've probably already said too much.. we appreciate YOU.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Warpslide on Wed Nov 11 18:14:03 2020
    I'm running on a Raspberry Pi, here is how I have my two events setup:

    Active │ Yes
    Description │ Toss incoming echomail
    Event Type │ Semaphore
    Exec Hour │ 0
    Exec Min │ 0
    Shell │ /home/pi/mystic/mutil mailin.ini
    Semaphore │ echomail.in|netmail.in
    Kill After │ echomail.in|netmail.in


    Active │ Yes
    Description │ Poll echomail
    Event Type │ Interval
    Exec Hour │ 1
    Exec Min │ 0
    Shell │ /home/pi/mystic/mis poll forced|/home/pi/mystic/mutil mailin.ini Semaphore │
    Kill After │

    Hope this helps.

    Jeez - people are posting such good information over the past day. Can I ask you, what are the 'semaphore' and 'kill after' lines? Mine are null, and ... while my setup works, I'd like to understand exactly whats going on or whats possible...

    I don't have semaphore or kill after set to anything; should I?



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to ryan on Wed Nov 11 18:20:33 2020
    Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

    Not a problem, you just need to spell out the absolute path like

    "/mystic/mis poll force" or whatever the syntax is.

    "/mystic/./mis poll force"

    the "./" always goes right before the command you are running; in standard linux, ubuntu, whatever flavor...

    just like when yer IN /mystic and you type "./mystic -cfg" to load up the config...

    you always type "./" before the command you want to run..

    ~/mystic/./mplc myfile.mps

    or whatever..



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Al@21:4/106.1 to paulie420 on Wed Nov 11 20:48:25 2020
    Re: Re: MIS POLL
    By: paulie420 to Al on Wed Nov 11 2020 05:57 pm

    You know, when I posted this it was more for the wondery of if I needed full paths or not; I actually do run ./mis send, too... and ./mis poll for another event...

    WHen I first started using linux this all caused me lots of wonder too.. :)

    ./ means current directory. Linux never looks for binary files to run in your current directory the way other OSs do, it only looks in the path. That's why you always need to add the ./ if you want to run a binary in your current directory.

    "./mis poll send" will send any mail in your outbound but will do nothing if there is nothing to go.

    "./mis poll 21:1/100" will poll 21:1/100 even if the outbound is empty.

    If I were a betting man, I think I'd say that under Linux, you can still just call it with ./ ... that is basically 'a full path' as long as mis runs in /mystic...

    Only if the file you want to run is in your current directory.

    It doesn't hurt to use a full path either, /mystic/mis poll send" or whatever the path is.

    I think for the Windows users maybe they are the ones that need to modify the commands when upgrading to a47... (With full pathnames; I know we all have to modify to mis...)

    On Windows, DOS and OS/2 the ./ isn't needed because those OSs will run a command in your current directory before looking in the path.

    Ttyl :-),
    Al

    ... Software means never having to say you're finished.
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Al@21:4/106.1 to paulie420 on Wed Nov 11 20:52:53 2020
    Re: Re: MIS POLL
    By: paulie420 to Al on Wed Nov 11 2020 06:01 pm

    Hey Al, thanks for posting this... I upgraded to a47 - are you stating that he continues to modify the a47 prealpha and a sysOp would be best served by updating the update every couple week?

    Yes, Mystic 1.12A46 is released. It's a done deal now. 1.12A47 is still a work in progress and there will likely be many new ones (prealphas) before A47 is released.

    Are you stating that he continues to modify that a47 build and I should check back to make sure I'm on the newest date??

    Yes, once he has done what he wants to do and tested that things are working according to plan he'll release an A47. At some point he'll release a 1.12 final but that may take a while.

    Ttyl :-),
    Al

    ... Proofread carefully to see if you any words out
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Avon@21:1/101 to paulie420 on Thu Nov 12 21:09:42 2020
    On 11 Nov 2020 at 06:02p, paulie420 pondered and said...

    Ok - I'm running the most current release too - am I correct in thinking that I should use my hub, as that address ... to poll?


    Yep, and you can also set up multiple selected polls if you wanted to on the one shell line if you wished.

    e.g.

    mis poll 21:1/100 | mis poll 3:770/1

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to paulie420 on Thu Nov 12 21:12:26 2020
    On 11 Nov 2020 at 06:04p, paulie420 pondered and said...

    Sorry for all the questions - but, is 'compiling your nodelist' running
    my mergenodelist.ini ??

    sorry for my language, In this case yes that's what I am referring to.

    I always add the newest nodelists to my /mystic/nodelists directory...
    and I run ./mutil mergonodelists.ini - which... merges all those nodelists. Are my nodelists 'compiled'???

    You can do this automatically such that your nodefile statement points to the file base directory your nodelist file sits in. Here's my current example at Agency

    nodefile=c:\bbs\files\fsx\fsx_node\fsxnet

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to paulie420 on Thu Nov 12 21:16:34 2020
    On 11 Nov 2020 at 06:08p, paulie420 pondered and said...

    I'd be much happier to hear that you love this hobby and all the moving parts within it- I've probably already said too much.. we appreciate YOU.

    Thanks for the kind words. I do love this hobby and am not planning on
    leaving it anytime soon.

    I think for all of us in this crazy world it's been a hell of a year with COVID-19 and other things. When I posted the last post I was feeling a bit
    down but honestly I don't know many of us that aren't having a few ups and downs during 2020.

    I'll get there. I hope you and yours are safe and well too.

    Best, Paul

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Thu Nov 12 21:18:08 2020
    On 11 Nov 2020 at 08:48p, Al pondered and said...

    ./ means current directory. Linux never looks for binary files to run in your current directory the way other OSs do, it only looks in the path. That's why you always need to add the ./ if you want to run a binary in your current directory.


    This is a basic how-to learning for me to. Thanks :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Al on Thu Nov 12 21:21:11 2020
    On 11 Nov 2020 at 08:52p, Al pondered and said...

    Yes, Mystic 1.12A46 is released. It's a done deal now. 1.12A47 is still
    a work in progress and there will likely be many new ones (prealphas) before A47 is released.
    Are you stating that he continues to modify that a47 build and I shou check back to make sure I'm on the newest date??

    Yes, once he has done what he wants to do and tested that things are working according to plan he'll release an A47. At some point he'll release a 1.12 final but that may take a while.

    Just to add to this, yes James creates multiple builds of Mystic when they
    are in pre-alpha.. one reason I'd suggested build dates were added some time ago to the tear lines.. it makes it easer for all to know what version is running on someones system :)

    Sometimes the community can see rapid development during a pre-alpha period
    and a full release follow quickly. Other times it may be many months of iterative changes in a pre-alpha before a full alpha sees the light of day as
    a public download.

    Hope that helps :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Al@21:4/106.1 to Avon on Thu Nov 12 00:56:25 2020
    Re: Re: Linux paths
    By: Avon to Al on Thu Nov 12 2020 09:18 pm

    On 11 Nov 2020 at 08:48p, Al pondered and said...
    ./ means current directory. Linux never looks for binary files to
    run in your current directory the way other OSs do, it only looks in
    the path. That's why you always need to add the ./ if you want to
    run a binary in your current directory.

    This is a basic how-to learning for me to. Thanks :)

    Here's a quick and dirty way to put your current directory on your path so these commands work the way they work on other OSs..

    PATH="$PATH:."

    This is not the linux, or unix way.. ;)

    Best if folks just use the ./ method.

    Ttyl :-),
    Al

    ... But that trick never works! -Rocky
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From pweck@21:3/113 to paulie420 on Thu Nov 12 00:58:52 2020
    You know, when I posted this it was more for the wondery of if I needed fullpaths or not; I actually do run ./mis send, too... and ./mis poll
    for anotherevent...

    If I were a betting man, I think I'd say that under Linux, you can still justcall it with ./ ... that is basically 'a full path' as long as mis runs in/mystic...

    that could be, but until i entered full paths, events were not working...i dunno, it could have been something else, but all works now. however, originally it did run with a problem as ./ ...

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to paulie420 on Thu Nov 12 01:00:15 2020
    everinterested in looking into it again :) The result code shoul if it's127 or similar then it's more likely the path issue I ref

    Where would I see the error code? Thanks

    In your mis WFC screen, go to events and if theres a '0' next to them there wasno errors on the last run.

    ok thanks, i'll check that

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From pweck@21:3/113 to paulie420 on Thu Nov 12 01:01:31 2020
    withwhat g00r00 is up to. I see there is a newer one (11/06) that I h to catchup with too.

    looks like pi didn't get the most recent update...yet

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Pweck's Retreat BBS (21:3/113)
  • From paulie420@21:2/150 to Avon on Thu Nov 12 05:00:03 2020
    sorry for my language, In this case yes that's what I am referring to.

    Yer fine - I thought I understood what you were saying. :P

    You can do this automatically such that your nodefile statement points
    to thefile base directory your nodelist file sits in. Here's my current example atAgency

    nodefile=c:\bbs\files\fsx\fsx_node\fsxnet

    Ah ha; lol, I was going to set my fsxNet file base to /mystic/nodelists ... but I get it - I get it... I will set each FTN to the file BASE location and that'll be much cleaner. :P Got it!! :P



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Avon on Thu Nov 12 05:02:42 2020
    Just to add to this, yes James creates multiple builds of Mystic when theyare in pre-alpha.. one reason I'd suggested build dates were added some timeago to the tear lines.. it makes it easer for all to know what version isrunning on someones system :)

    I think from now on, I'll stick to the ALPHA. I wanted to play with and use the 'marquee' feature - but... didn't think about any issues/bugs that may OR MAY NOT be in a preALPHA.

    It is a little harder for a newbie to understand; but.. I think I'm grasping that for me, not a total BBS genius, I should be on a46. :) Thanks to both of you for explaining.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to pweck on Thu Nov 12 05:06:10 2020
    Yeah, in the case of the prealphas it's a good idea to keep up t withwhat g00r00 is up to. I see there is a newer one (11/06) tha to catchup with too.

    looks like pi didn't get the most recent update...yet

    Thanks for that; I guess since I went to a47 I need to checkup on these releases. Next time I'm going to stick with the alpha... lol; for a user like me who doesn't want to keep upgrading with every small change, I should stick on the last 'complete' version. In this case a46....?? LOL.

    With other github projects, theres just a stable version, that doesn't change. And a bleeding edge, or alpha - that does get updates. :/ Hard to understand, with so many developers and the ways the describe their releases.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Warpslide@21:3/110 to paulie420 on Thu Nov 12 11:05:31 2020
    On 11 Nov 2020, paulie420 said the following...

    Just hope that you know that PLENTY of folks in this BBS community both pa> appreciate, count on and know what YOU do for this scene.

    I'd be much happier to hear that you love this hobby and all the moving parts within it- I've probably already said too much.. we appreciate YOU.

    Couldn't agree with this more. I got back into the BBS scene because of covid (wanted something familiar and that made me feel good).

    That's when I discovered Mystic and by extension the Mystic Guy's videos on YouTube. Safe to say I wouldn't be on here without Paul & everything he does for the community.

    Jay

    ... I went to bed with my contact lenses in. My dreams have never been clearer

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Warpslide@21:3/110 to paulie420 on Thu Nov 12 11:13:13 2020
    On 11 Nov 2020, paulie420 said the following...

    Jeez - people are posting such good information over the past day. Can I ask you, what are the 'semaphore' and 'kill after' lines? Mine are null, and ... while my setup works, I'd like to understand exactly whats going on or whats possible...

    A semaphore is a file created in the mystic/semaphore directory. When echomail is received by the bink server Mystic will create an echomail.in file in the semaphore directory. Likewise when you post a message in a message base Mystic will create an echomail.out file.

    If you have an event monitor for these semaphores (I believe Mystic checks the directory once a minute) then you can have things run more often, almost in real time.

    e.g.

    You post a message here in this message base. Mystic creates mystic/semaphore/echomail.out

    You have an event looking for echomail.out which runs:
    mutil mailout.ini|mis poll send

    The kill after line deletes that semaphore so the event won't run continuously.

    So the way I have Mystic setup, each time I post a message it's sent out usually within a minute, rather than waiting for an event to run every so often to collect mail and send it out.

    Jay

    ... There was a kidnapping at school yesterday. Don't worry though, he woke up

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From ryan@21:1/168 to paulie420 on Thu Nov 12 08:50:14 2020
    "/mystic/./mis poll force"

    This is incorrect. If you use absolute path, you don't put the '.' character
    in there. I.e., you just use "/mystic/mis poll force". If you want to run a binary from the current directory you are in, you then put the '.' character, i.e. if your present working directory is /mystic/ already, you just use
    "./mis poll force".

    the "./" always goes right before the command you are running; in
    standard linux, ubuntu, whatever flavor...

    Only if you are trying to run a binary in the directory that you are
    currently in.

    you always type "./" before the command you want to run..

    ~/mystic/./mplc myfile.mps

    Negative. :) _ONLY_ put the '.' if you're trying to run a binary from your current directory.

    --- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
    * Origin: monterey bbs (21:1/168)
  • From Warpslide@21:3/110 to Al on Thu Nov 12 11:59:06 2020
    On 11 Nov 2020, Al said the following...

    ... Proofread carefully to see if you any words out

    I read this fine the first time, but then I saw proofread carefully...

    Jay

    ... Is your iPad making you fall asleep? I can help, there's a nap for that

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Warpslide@21:3/110 to Al on Thu Nov 12 12:01:00 2020
    On 12 Nov 2020, Al said the following...

    PATH="$PATH:."

    This is not the linux, or unix way.. ;)

    Best if folks just use the ./ method.

    Just don't tell them about: alias dir='ls -h' ;)

    Jay

    ... I like bowling. Seriously, it's right up my alley.

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Black Panther@21:1/186 to paulie420 on Thu Nov 12 12:48:08 2020
    paulie420 wrote to Avon <=-

    nodefile=c:\bbs\files\fsx\fsx_node\fsxnet

    Ah ha; lol, I was going to set my fsxNet file base to /mystic/nodelists ... but I get it - I get it... I will set each FTN to the file BASE location and that'll be much cleaner. :P Got it!! :P

    Just remember it is case sensitive! If the nodelist is in caps, you will need:

    nodefile=/home/mystic/fsx/fsx_node/FSXNET

    (Yes, I'm speaking from experience on this one... ) ;)


    ... "Hex Dump" - Where Witches put used Curses?
    ___ MultiMail/Linux v0.52.1(RCS)

    --- Mystic BBS/QWK v1.12 A47 2020/11/06 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Black Panther on Fri Nov 13 11:21:31 2020
    On 12 Nov 2020 at 12:48p, Black Panther pondered and said...

    Just remember it is case sensitive! If the nodelist is in caps, you will need:

    nodefile=/home/mystic/fsx/fsx_node/FSXNET

    I think this is no longer a problem... from memory James did set it to look
    for both upper and lower cases when it scanned... mostly due to feedback
    about this very niggle in the past :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Black Panther@21:1/186 to Avon on Thu Nov 12 15:29:28 2020
    On 13 Nov 2020, 11:21a, Avon said the following...

    nodefile=/home/mystic/fsx/fsx_node/FSXNET

    I think this is no longer a problem... from memory James did set it to lookfor both upper and lower cases when it scanned... mostly due to feedbackabout this very niggle in the past :)

    Ooops. I missed that one. I just verified it is no longer case sensitive. :)


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2020/11/06 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Black Panther@21:1/186 to Warpslide on Thu Nov 12 17:27:44 2020
    On 12 Nov 2020, 12:01p, Warpslide said the following...

    Just don't tell them about: alias dir='ls -h' ;)

    sudo apt install sl

    That way you know when you misspell ls on the command line. ;)


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2020/11/06 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From paulie420@21:2/150 to Warpslide on Thu Nov 12 17:15:36 2020
    I'd be much happier to hear that you love this hobby and all the movi parts within it- I've probably already said too much.. we appreciate

    Couldn't agree with this more. I got back into the BBS scene because of covid(wanted something familiar and that made me feel good).

    That's when I discovered Mystic and by extension the Mystic Guy's videos onYouTube. Safe to say I wouldn't be on here without Paul & everything he doesfor the community.

    Jay

    ... I went to bed with my contact lenses in. My dreams have never been

    LOL - Weird; for some reason I thought you have been around much longer. With a name like warpslide, I guess it makes you instantly uber cool. w00t w00t, daddio!!!



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From paulie420@21:2/150 to Warpslide on Thu Nov 12 18:14:25 2020
    A semaphore is a file created in the mystic/semaphore directory. When echomailis received by the bink server Mystic will create an echomail.in file in thesemaphore directory. Likewise when you post a message in a message base Mysticwill create an echomail.out file.

    If you have an event monitor for these semaphores (I believe Mystic
    checks thedirectory once a minute) then you can have things run more often, almost inreal time.

    e.g.

    You post a message here in this message base. Mystic creates mystic/semaphore/echomail.out

    You have an event looking for echomail.out which runs:
    mutil mailout.ini|mis poll send

    The kill after line deletes that semaphore so the event won't run continuously.

    So the way I have Mystic setup, each time I post a message it's sent out usually within a minute, rather than waiting for an event to run every
    so oftento collect mail and send it out.

    Jay

    Great explanation - copied to my mystic_txt folder.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Al@21:4/106.1 to Warpslide on Thu Nov 12 20:07:08 2020
    Re: Re: MIS POLL
    By: Warpslide to Al on Thu Nov 12 2020 11:59 am

    ... Proofread carefully to see if you any words out

    I read this fine the first time, but then I saw proofread carefully...

    Yep, that's a tricky one! ;)

    Ttyl :-),
    Al

    ... Put on your seatbelt - I'm gonna try something new!
    --- SBBSecho 3.11-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Xenos@21:4/147 to Black Panther on Fri Nov 13 14:06:22 2020
    RE: Re: Linux paths
    BY: Black Panther (21:1/186)

    On Thursday, November 12, 2020 at 16:27, Black Panther (21:1/186) wrote:

    On 12 Nov 2020, 12:01p, Warpslide said the following...

    Just don't tell them about: alias dir='ls -h' ;)

    sudo apt install sl

    That way you know when you misspell ls on the command line. ;)


    Doncha just love 'em trains? :D

    A .-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-.
    /*\ | /\liens' /\lcove! WWIV on Linux - Taguig, Metro Manila, Philippines |
    / v \`-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=[ WWIV Reg. #30282 ]-=-=-=-=-=-=-=-'

    --- WWIV 5.3.0.dev-xenos
    * Origin: /\lien's /\lcove! WWIV 5 on Linux | aliens.free.net.ph (21:4/147)
  • From Black Panther@21:1/186 to Xenos on Thu Nov 12 23:30:48 2020
    On 13 Nov 2020, 02:06p, Xenos said the following...

    sudo apt install sl

    Doncha just love 'em trains? :D

    I sure do. I also see it a lot. ;)

    I had the same issue in dos. I didn't think typing a two or three character command would cause that many spelling issues...


    ---

    Black Panther(RCS)
    aka Dan Richter
    Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    http://github.com/DRPanther
    The sparrows are flying again...

    --- Mystic BBS v1.12 A47 2020/11/06 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Warpslide@21:3/110 to paulie420 on Fri Nov 13 08:17:44 2020
    On 12 Nov 2020, paulie420 said the following...

    LOL - Weird; for some reason I thought you have been around much longer. With a name like warpslide, I guess it makes you instantly uber cool. pa> w00t w00t, daddio!!!

    LOL, well I DID run a Telegard BBS back in the late 90's but I honestly don't remember which handle I used back then. It wasn't until I moved out of my parent's house & got my first DSL connection that I started using Warpslide around 2001.

    Jay

    ... How do you invite a dinosaur for lunch? Tea, Rex?

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)