| Sysop: | KK4QBN |
|---|---|
| Location: | Chatsworth, GA |
| Users: | 49 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 59:25:39 |
| Calls: | 905 |
| Calls today: | 0 |
| Files: | 138,634 |
| U/L today: |
0 files (0K bytes) |
| D/L today: |
799 files (150M bytes) |
| Messages: | 26,341 |
| Posted today: | 0 |
The message base allocation method shouldn't make any difference
with the problem you're describing.
Since no one else is reporting the problem you're seeing, I suggest
trying to "undo" some of your mods. Or just as a test, don't use of
the 3rd party mods (e.g. message reader) you might be using.
I've actually seen what I think he is describing. It seems to happen when I reply to a message using my reader. It happens rarely and randomly, so it's difficult to reproduce. I've noticed it in Windows (I think Psi-Jack is running Synchronet in Linux?).
The other day I made a small JavaScript script that opens a sub-board with a MessageBase object, lets a user post a message while that MessageBase object is open, then closes the MessageBase object. I was trying to reproduce the issue in Linux where if a JS script has a MessageBase open and lets the user post a message in that sub-board, the MessageBase wasn't getting updated as far as the number of messages. I ran that small script on my Linux test setup, and while that script didn't reproduce that issue, I did see it crash Synchronet multiple times after I had saved my message. I tried it in my Windows Synchronet setup, and I didn't see it causing a crash there. This is the code (substitute the value of the subCode variable with a valid sub-board code on your BBS):
load("sbbsdefs.js");
subCode = "loc_general";
var msgbase = new MsgBase(subCode);
if (msgbase.open())
{
console.print("\1n\r\n# of messages (before posting): " + msgbase.total_msgs
+ "\r\n\1p");
var msgHdr = msgbase.get_msg_header(true, msgbase.total_msgs-1, true);
if (msgHdr != null)
{
bbs.post_msg(subCode, WM_NONE, msgHdr);
console.print("\1n\r\n# of messages (after posting): " + msgbase.total_msgs
+ "\r\n\1p");
}
msgbase.close();
}
I'm not sure I'd consider 4DOS a limitation, since (I believe) it's
fully compatible with command.com. It's cool to hear that 4DOS is
now freeware. I used to use 4DOS in the early 90s, when DOS was my
primary OS, and I thought it provided some useful enhancements over
the command.com included with MS-DOS.
I loved 4dos. Such awesome enhancements for command.com's pointlessly lobotomized batch features.
Re: Posting a message with messagebase open
By: Digital Man to Nightfox on Wed Jul 15 2015 16:46:12
I just committed an additional file stream flush to the SMB
"get status" function (in src/smblib). Please try this and if
that doesn't fix it, provide more details or better yet, a
small script to reproduce the problem (e.g. using jsexec).
I hadn't actually commited the flush call yet. I just did. Please
try again.
I updated my Synchronet build on my Linux test system, and that seems
to have fixed the issue I was seeing.
Okay, good. There will probably be other flush-related commits to smblib since this highlights an issue with stale read-data that I was not aware of.
This does not explain any crashes or unintended program exits you were seeing.
I just wonder if the same issue MAY had been causing the disconnects
as well. As you say, it doesn't explain it, but if it resolves it at
the same time...
I can't think of any logical connection between the two things.
I just wonder if the same issue MAY had been causing the
disconnects as well. As you say, it doesn't explain it, but if it
resolves it at the same time...
I can't think of any logical connection between the two things.
Yeah, definitely isn't. A message or two after this reply I made, I
was dropped just while putting in the To, then Subject, then boom, disconnect.
So, Not sure. Definitely still happening, with current CVS codebase.
Does it happen when you don't use the custom message reader mod?
If it's a JS exception causing the termination, there should (normally) be some indication in the log output. I suppose it's possible that the script could handle the exception (whatever it is) and just terminate silently, but that's not normal.
The problem may actually be SyncTERM itself dropping the connection..
A potential situation I pondered.
The way I'm currently testing this theory is sadly by using NetRunner.
I hate this particular terminal app because it's so slow and clunky,
and doesn't even support rlogin or ssh like I usually use. heh. And
it's slow, even over LAN.
So far, though, using NetRunner, I have yet to see a single
disconnect, but I'm going to continue using it for the rest of this
week to see.
And you could try different protocols in SyncTERM (e.g. Telnet instead of SSH).
So far, though, using NetRunner, I have yet to see a single
disconnect, but I'm going to continue using it for the rest of this
week to see.
And you could try different protocols in SyncTERM (e.g. Telnet instead
of SSH).
That reminds me, several years ago I noticed that when I was connected to my BBS via SSH (using SyncTerm), I would get disconnected from my BBS after some amount of time. It didn't seem to be related to posting messages or anything in particular. But I noticed that seemed to be fixed in more recent builds of Synchronet/SyncTerm.
Re: Posting a message with messagebase open
By: Psi-Jack to Nightfox on Sat Jul 11 2015 21:19:17
This is another message from you that has somehow migrated to another board - I saw this in the Sports board on Dove-Net. This was originally in the Synchronet JavaScript board.