I just updated the pre-alpha build which should address the BINKP issue
as well as introduce a new message linking system that works better.
Hey all,
I just updated the pre-alpha build which should address the BINKP issue
as well as introduce a new message linking system that works better.
just pumping them out. reminds of the 1.08 alpha days.. ;)
Hey all,
I just updated the pre-alpha build which should address the BINKP issue
as well as introduce a new message linking system that works better.
I just updated the pre-alpha build which should address the BINKP issue
as well as introduce a new message linking system that works better.
Whatever you did with this new build seems to have fixed issues with my scanning the full message base using golded. Before the update golded would freeze and lockup. It does *Not* do that any more after packing and
Nov 08 14:46:37 Polling BINKP node 1:322/756
Nov 08 14:46:37 Connecting to necrobbs.strangled.net
Nov 08 14:46:38 Connected
Nov 08 14:46:38 System Necronomicon BBS
Nov 08 14:46:38 SysOp Necromaster
Nov 08 14:46:38 Mailer Mystic/1.12A35 binkp/1.0
Nov 08 14:46:38 Sending: 040ee954.pkt (13,081 bytes)
Nov 08 14:46:38 Sending: DBNET.tic (756 bytes)
For the last three hours it's been running fine as far as I can tell and more importantly Fidopoll is not stalling, nor am I seeing any session timeout messages in the MIS2 logging for BinkP - so that's looking good James.
Could you please add Date fields to the MIS2 logging as per Fidopoll logging
Current MIS2
+ 10:07:37 BINKP 1-System Mystic Pi BBS
The other thing I'm kinda noticing with this change to MIS2 is the need
to search the MIS2 log for all types of logging in the one log e.g.
events firing vs BinkP connects etc. I'm of mixed view about it. I like
So perhaps something that could be configured in MIS2.INI that would
allow for logging to be more configurable? e.g. SysOp could enable
Another thought, do you think line lengths in MIS2 logs should be set to 79 chars and then wrapped so when posting as per above things look more consistent and are not altered by some lines being longer than 80 chars?
Can I suggest a re-design of the Events tab display? I would add additional columns for each event that displays the last date/time an event ran and the last recorded error code it returned. You could
The 'Connections' tab. could use an extra column that displays the connection date/time against each recorded connection. I suggest the display should be sticky - so instead of displaying only active connections, display the last X connections (most recent at the top) and
Another thought I had was pressing enter on a specific connection entry
on this screen might reveal other data related to that connection that
had been logged but was otherwise unable to be displayed on the single line.
Having a day off today so have more time to play!
A readability thing, really. But maybe just adding the date is better? Here's an example of what I mean:
---------- Mystic v1.12 A36 Mon, Nov 06 2017 (loglevel 3)
+ 23:27:10 MANAGER Starting event system
+ 23:27:10 MANAGER Starting 3 server(s)
+ 23:27:10 EVENT Starting 2 event(s)
Date Mon, Nov 07 2016
+ 01:13:15 TELNET Connect on slot 1/8
So maybe something like this for all of the logs? :
--------------- Mystic v1.12 A36 2017/11/08 (loglevel 3)
20171108 204521 MANAGER Starting event system
events firing vs BinkP connects etc. I'm of mixed view about it. I li
I'm mixed about it too. The reason I have those server "IDs" on each
line is so you can do stuff like: "type mis2.log | grep BINKP" to see
all entries from the BINKP server. This essentially "creates" a server_binkp.log.
I was also thinking about adding a "filter" option in the window itself
in the UI so you can filter out everything except a particular server type.
Logging will be more configurable when the logging revamp is done, which its not yet. Every alpha has logging changes though its just not happening all at once.
Another thought, do you think line lengths in MIS2 logs should be set 79 chars and then wrapped so when posting as per above things look mo consistent and are not altered by some lines being longer than 80 cha
Yes, I may do that. MIS already does it I think.
Can I suggest a re-design of the Events tab display? I would add additional columns for each event that displays the last date/time an event ran and the last recorded error code it returned. You could
This is a great idea and something I already planned to do. I realized I wanted to do that as I was building in the new event system, I just haven't gone back yet to fix that up.
display should be sticky - so instead of displaying only active connections, display the last X connections (most recent at the top)
I think the last X connections might be more appropriate on the stats
tab, but maybe I can put it in both. I think adding connection time is
a good idea.
Connections is supposed to show you what is current. With that said, I think you're right that adding the connection time would be a nice addition.
There are going to be quite a lot of things you will be able to do by pressing enter on a connected user, but not until "NodeSpy" is merged
into MIS2. That isn't happening until after I get the rest of the
server in MIS2. After that the plan is probably going to be to merge in QWKPOLL, FIDOPOLL and NODESPY all into MIS2.
You'll be able to do all sorts of things from the UI like chat and snoop and use a terminal, but also from the command line. Things like "mis2 terminal" "mis2 snoop 1" "mis2 fido forced" "mis2 qwk all" "mis2
nodelist <searchtext>" "mis2 killbusy" "mis2 nodespy"
Converging all of these things together opens up some new possibilities.
The final step will be to merge MYSTIC and MIS2 together and just call
the who thing "MYSTIC" just like the way the Mystic 2 demo was set up.
Having a day off today so have more time to play!
Great! Thank you for the feedback and all of the testing it is very much appreciated.
Great to see. I also did a lot of testing with IREX as well, and made some small changes that will allow it to work better for you (I hope).
I know it is something you were struggling with.
--------------- Mystic v1.12 A36 2017/11/08 (loglevel 3)
20171108 204521 MANAGER Starting event system
Agreed but I do prefer the layout of the first example as it transcends the different way we look at DD/MM/YY or MM/DD/YY depending on where you are located on the globe. So yep, can we take option one please :)
True and I agree, but, if you're a windows bloke with little grep skills it may just be he will need an extra helping hand :) However you choose
to do it, if you choose to do it :)
Irex receives the first file fine then dropped connection when the second file starts. Mystic log will show 1-sent while the irex\in shows the
Irex receives the first file fine then dropped connection when the second file starts. Mystic log will show 1-sent while the irex\in shows the
first file completed and the second filename.??? as zero bytes. So that issue still remains when talking with a irex mailer.
Maybe a hybrid of the two would be good:
-------------------- Mystic v1.12 A36 Mon, Nov 06 2017 (loglevel 3)
23 Aug 2017 11:11:11 MANAGER Starting event system
23 Aug 2017 11:11:11 MANAGER Starting 3 server(s)
Or I could make year 2 digits
------------------ Mystic v1.12 A36
23 Aug 17 11:11:11 MANAGER Starting event system
There is grep for windows that you can just drop in a system path, it works well for that stuff. I know its not installed by default but for now it will give you want you need.
You've seen this with the very latest version? I have tested large
number of files with IREX and it worked but that was a few days ago
maybe something changed.
I am not able to reproduce this at all with the latest builds. I've tested large amounts of files both being sent and received by MIS2. Are you talking about FidoPoll or MIS2? I just ran a test again with no problems:
---------- Mystic v1.12 A36 2017/11/09 Thu, Nov 09 2017 (loglevel 3)
MIS2 my log looks different then your test.net does, plus your's also doesn't show multiple network # of file queries..so I'm guessing your's are getting sent from file boxes? Here is a old mystic point system
Can you ask them to show you their IREX settings for your address so I
can see what options they have selected? Maybe that would help.
Use NR mode No Use CRC mode Yes
Use CRAM-MD5 Yes Use MD5 mode Yes
[] Toss to/from a BinkP site
Site's address fluph.darktech.org
Site's hours 0:00-24:00
Connection timeout 60 seconds
Block size 4096 bytes
Use NR mode No Use CRC mode Yes
Use CRAM-MD5 Yes Use MD5 mode Yes
Default domain fidonet
---------- Internet Rex 2.31 (Win95/NT 32-bit), Thu Nov 9 19:46:52
Use NR mode No Use CRC mode YesI'm not sure what effect it would have, but Mystic doesn't do CRC mode, its not part of the main BINKP specification and I don't know what Use
Use CRAM-MD5 Yes Use MD5 mode Yes
MD5 mode would be either.
Looking at my test setup though, I have them enabled (they must be by default) and all of my tests work fine here... So I don't think its
going to help to change them.
I will put a debug version on the prealpha area for Windows if you'd
like to capture a debug log.
This is what works with my Irex connections:
change CRAM-MD5 to no
change USE MD5 to no
I get multiple files sent this way and no connection issues.
I'll change the CRC mode and MD5 to no. But I prefer the passwords remain encrypted, so will just keep the use cram-md5. Then test it to see what happens. Thanks for sharing your findings with me Zazz.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 3 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 146:14:45 |
| Calls: | 2,129 |
| Calls today: | 2 |
| Files: | 11,149 |
| D/L today: |
31 files (9,999K bytes) |
| Messages: | 951,105 |