I've updated pre-alphas for Intel Linux and Windows. Trying a few new things here with this build. Those couple of you who have reported a crash this should help us identify how to fix it.
Thanks coming up noon over here, will update tonight when home :)
Great! The binaries should make a .mem file now which will hopefully
give us some insight to whatever the crash is that happens. The
downside is I accidentally compiled this version with BINKP debug
logging turned on, so those log files will be huge.
That's totally fine. I am hopefully leaving work early today so may get them in place in the coming hours.. then it's just a waiting game I
guess.
On the box that the crash happened I am running four instances of MIS
now.
That's totally fine. I am hopefully leaving work early today so may g them in place in the coming hours.. then it's just a waiting game I guess.
Yep, sounds great. I just finished work and I am now off until Jan 2nd.
I couldn't be more excited to get a vacation.
On the box that the crash happened I am running four instances of MIS now.
That is awesome! I can't thank you enough for how much Mystic gets
pushed because of your setup, and how patient you are when a hard to get serious bug pops up!
The memory dump log should (hopefully) estimate an actual line of code or location where the error happens which will obviously be a great way to pinpoint issues! It will also trap memory leaks too.
I had shut the server down and copied all logs and .mem files to a temp directory before doing so. I also checked the semaphore directory and could not find any echomail.in waiting etc. just the mis.bsy semaphore.
I had a quick look in echomail\out\fidonet and could not see any *.bsy files before running the overdue toss.
My wife probably thinks I already spend too much time on it as it is!
:)
I've updated the prealpha with some little changes just in case anyone is interested.
I've updated the prealpha with some little changes just in case anyone is interested.
On 12/20/18, g00r00 pondered and said...
I've updated the prealpha with some little changes just in case anyon interested.
If I was not at work right now I'd be on to it :) But instead I have to wait 8 hours - sigh :)
I've updated the prealpha with some little changes just in case anyone is interested.
I've updated the prealpha with some little changes just in case
anyone is interested.
[snip]
+ Message Base editor now has a /A command to select all bases.
+ File Base editor now has a /A command to select all bases.
+ File Base editor now has a /G Global Editor similar to the Message
Base editor
[snip]
Those additions will save folks a lot of time, especially the last one
- thanks!
+ Message Base editor now has a /A command to select all bases.
+ File Base editor now has a /A command to select all bases.
+ File Base editor now has a /G Global Editor similar to the Message
Base editor
+ Message Base editor now has a /A command to select all bases.
+ File Base editor now has a /A command to select all bases.
+ File Base editor now has a /G Global Editor similar to the Message
Base editor
Those additions will save folks a lot of time, especially the last one -
Yes, I've been meaning to add that in for a long time. I'd like to do a similar version for users and possibly echomail nodes as well.
But as of now I am focused on a new larger feature that I think you will really love :) I don't want to say too much more until I see it
starting to work but I will need your help testing!
But as of now I am focused on a new larger feature that I think you w really love :) I don't want to say too much more until I see it starting to work but I will need your help testing!
I have a pretty good hunch I know what that may be, and thanks!
Well, I finished it today after a good 10 hour programming session. I am about to upload it when I log off.
That's totally cool - thanks! I'm going to try and play with this
tonight and will also move to update NET 1 HUB so I can better test the other encryption features you have added in recent pre-alphas between
test nodes and a working HUB.
You might think I'm a tad nutty but could the feature be extended to echomail posts in some form? So a post could be encrypted and decrypted
in a conference in such a way that only certain echonodes could encode/decode it. I'm not good at mentally thinking this through at the early hour I type this. But I thinking about how you can use PGP to
encode a message to more than one party in one go using public/private keys etc. Dunno.. I was just fishing for a way to have 'one to many'
even if that worked you still end up with perhaps decoded echomail for a message board that can be viewed by all users given access to the message base on a specific node in the network.
Perhaps the encode/decode could be keyed to the individual BBS user account, so taking the idea of keys for echonode down another level. I guess then you can have a user X who can encode/decode posts in echomail area Y that in turn can only be encoded/decoded between certain nodes
who also share the correct keys..
I've updated the prealpha with some little changes just in case anyon interested.
[snip]
+ Message Base editor now has a /A command to select all bases.
+ File Base editor now has a /A command to select all bases.
+ File Base editor now has a /G Global Editor similar to the Message
Base editor
That's totally cool - thanks! I'm going to try and play with this
tonight and will also move to update NET 1 HUB so I can better test the other encryption features you have added in recent pre-alphas between
test nodes and a working HUB.
If you need another guinea pig to test with, count me in! :)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 220:21:38 |
| Calls: | 6,622 |
| Calls today: | 4 |
| Files: | 12,171 |
| Messages: | 5,318,023 |