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 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 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 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)
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.
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??
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.
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....I noticed that my events are not running, specifically for the ./mis
do you run something like
./mis poll 21:1/100
Av> if it's just ./mis poll thenthat'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?
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.
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.
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
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 use ./mis poll send
That will send out whatever is waiting in the outbound.
./mis poll 21:1/100Yes. 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....
--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)
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.
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!
Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced
correct?
yes it works when I manually run it from a command prompt. automated seems hit and missYes. 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?
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>
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.
./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 thefull path /home/pi/mystic/misthanks, 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 │ YesThank you!
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 │
Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?
Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?
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.
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
Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced
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
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
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.
Have you compiled your nodelist?
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.
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.
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.
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...)
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?
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??
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?
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'???
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.
./ 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.
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.
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 :)
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...
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.
withwhat g00r00 is up to. I see there is a newer one (11/06) that I h to catchup with too.
sorry for my language, In this case yes that's what I am referring to.
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
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 :)
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
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.
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...
"/mystic/./mis poll force"
the "./" always goes right before the command you are running; in
standard linux, ubuntu, whatever flavor...
you always type "./" before the command you want to run..
~/mystic/./mplc myfile.mps
... Proofread carefully to see if you any words out
PATH="$PATH:."
This is not the linux, or unix way.. ;)
Best if folks just use the ./ method.
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
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 :)
Just don't tell them about: alias dir='ls -h' ;)
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
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
... Proofread carefully to see if you any words out
I read this fine the first time, but then I saw proofread carefully...
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. ;)
sudo apt install sl
Doncha just love 'em trains? :D
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!!!
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,045 |
| Nodes: | 15 (1 / 14) |
| Uptime: | 63:49:26 |
| Calls: | 500,408 |
| Calls today: | 11 |
| Files: | 95,209 |
| D/L today: |
1,683 files (496M bytes) |
| Messages: | 465,011 |
| Posted today: | 2 |