Digital Man wrote to Bill McGarrity <=-
Re: Re: Packet PW
By: Bill McGarrity to Digital Man on Wed May 04 2016 12:51 am
Digital Man wrote to Joe Delahaye <=-
Re: Re: Packet PW
By: Joe Delahaye to Bill McGarrity on Tue May 03 2016 05:52 pm
I also noticed a "Comment" was added in the form of the AREAFIX password we used.
Saw that, but not sure what that is about.
Can you elaborate? I don't know what is meant by this... a comment in the sbbsecho.ini file?
In echocfg when you bring up linked nodes, to the right of node # there was my areafix password to that node. When I viewed that particular node information, the areafix pw was there along with a new section called Comment which had the same pw in it. I removed the Comment entry and esc out and the "comment" was no longer seen on the Linked Nodes column. It only happened to Robert Starr's node.
That sounds like a bug. Can you re-run sbbsecho_upgrade.js (the latest revision) on your original sbbsecho.cfg, just as a test, and look at
the resulting sbbecho.ini file and see if that anomoly exists? Or maybe
it pops up after the first time you run echocfg with a newly upgraded sbbsecho.ini?
If I can reproduce it (either the erroneous "comment" or a packet
password that was not previously configured), then I can fix it. So
far, I've been unable to reproduce these sightings.
Digital Man wrote to Bill McGarrity <=-
Re: Re: Packet PW
By: Bill McGarrity to Digital Man on Wed May 04 2016 08:06 pm
That sounds like a bug. Can you re-run sbbsecho_upgrade.js (the latest revision) on your original sbbsecho.cfg, just as a test, and look at the resulting sbbecho.ini file and see if that anomoly exists? Or maybe it pops up after the first time you run echocfg with a newly upgraded sbbsecho.ini?
FYI, didn't happen this time....
Ugh. The mystery remains then.
Nothing appeared in the area next to Robert's node # (316:77/1)
What about the packet vs. areafix passwords? There were claims that the packet passwords were being "set" (in sbbsecho.ini) that weren't previously (in sbbsecho.cfg)?
Is there a debug mode I can use in the jsexec?
Not one that would help with this test.
Joe Delahaye wrote to All <=-
I have not seen it referred to, so I am wondering. Since shortly after the upgrade to sbbsecho.v3, I had one node not tossing mail all of a sudden. Looking at the log files, there was an entry for a pcket PW missing. Found "" expected Password. I never had a packet PW with
this node. He does not have one configured for me either. Yesterday another contact the same. No Packet Pw configured ever, and yet it requires one now. It just occurred to me that both these links are running the same mailer software, one of them is the author of DB, but
I have other links also running DB, and so far no problem with them
To be precise, it is the session PW that is now required as the Packet
PW as well for some reason.
Joe Delahaye wrote to Bill McGarrity <=-
Both my links are running DB. Nick and Roger, so far. Just waiting to see if personal packets from Ward, who also runs DB, is going to end up the same way. At this time, I dont know if SBBSEcho is somehow adding
the session pw as a packet pw, or if it is DB, but like you said, this started with v3.
I also noticed a "Comment" was added in the form of the AREAFIX password we used.
Saw that, but not sure what that is about.
Digital Man wrote to Joe Delahaye <=-
Re: Re: Packet PW
By: Joe Delahaye to Bill McGarrity on Tue May 03 2016 05:52 pm
I also noticed a "Comment" was added in the form of the AREAFIX password we used.
Saw that, but not sure what that is about.
Can you elaborate? I don't know what is meant by this... a comment in
the sbbsecho.ini file?
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 130:59:16 |
Calls: | 8,198 |
Files: | 15,446 |
Messages: | 913,776 |