For example, FidoNet may have a SYSOP echo, but WWIVnet may also have a SYSOP echo, creating confusion amongst the file and for a re-import. Could a change be put in to reflect
If you are running multiple FTN-based message areas, is the badareas.lst updated generically? I believe it is.
For example, FidoNet may have a
SYSOP echo, but WWIVnet may also have a SYSOP echo, creating confusion amongst the file and for a re-import.
Could a change be put in to reflect
the Message Group for the creation of a new badareas.lst file, e.g. fidonet-badareas.lst, micronet-badareas.lst, etc.?
Or, keep the file but
group them with tags that can be interpretted by the Import Areas function of SCFG:
If you have multiple FTNs with echo-tag collisions, you'll need to run multiple SBBSecho configurations (with different area files) to keep them separate. Both the area file and the bad area file names and paths are configurable in your sbbsecho configuratoin. So using multiple SBBSecho configurations would be the first step to the solution there.
Re: badareas.lst
By: Digital Man to Dream Master on Thu Jan 28 2021 08:00 pm
If you have multiple FTNs with echo-tag collisions, you'll need to run multiple SBBSecho configurations (with different area files) to keep them separate. Both the area file and the bad area file names and paths are configurable in your sbbsecho configuratoin. So using multiple SBBSecho configurations would be the first step to the solution there.
There is an allowance for bad area file names for different echo groups?
There is an allowance for bad area file names for different echo groups?
No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.
No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.
Re: badareas.lst
By: Digital Man to Dream Master on Fri Jan 29 2021 07:33 pm
No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.
I think I found a problem. Although sbbsecho.ini can be split off into individual FTN files (fidonet.ini, scinet.ini, ...), tickit.js only parses sbbsecho.ini. Would it be possible to put in an echo configuration to specify those individual configuration files, for example:
[TickIT]
EchoCfg1=../ctrl/fidonet.ini
EchoCfg2=../ctrl/scinet.ini
EchoCfg3=../ctrl/micronet.ini
.
.
.
I've purged my sbbsecho.ini (well, renamed it to sbbsecho.ini.old) and can see in the logs that TickIT is looking for the file to parse. Unless you tell me there's a way to hack the crap out of sbbsecho.ini, I'm kind of at a loss how to do it any other way.
In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.
Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) - anyway, so I'm wondering if perhaps you're trying to solve a non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding, maybe no other SBBSecho users are also on WWIVnet (seems unlikely).
In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.
If you still want to go the multiple configs route, you should now be able to pass a unique configuration filename on the command-line to tickit.js (e.g "?tickit fidotick.ini")
And then in within that configuration file, specify "echocfg=fidoecho.ini", and that would link that fidotick.ini to fidoecho.ini.
Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 02:35 pm
Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) - anyway, so I'm wondering if perhaps you're trying to solve a non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding, maybe no other SBBSecho users are also on WWIVnet (seems unlikely).
My problem is the monolithic sbbsecho.ini file and my desire to split off inbound, outbound, and nonsecure into their own directory structures:
FidoNet:
/sbbs/fido/_fidonet/outbound
/sbbs/fido/_fidonet/inbound
/sbbs/fido/_fidonet/nonsecure
SciNet:
/sbbs/fido/_scinet/outbound
/sbbs/fido/_scinet/inbound
/sbbs/fido/_scinet/nonsecure
I've now received multiple TICs coming in that are from multiple FTNs with the same filename (and it pisses me off). For example, someone that is sending a file not from the FidoNet FTN but from another FTN, is sending the latest FidoNet nodelist/nodediff to me. Where my problem comes in is when something like this happens:
All this shit can't be processed and this is before I split off into individual echocfg files. TickIT barfed when trying to process this. All the file areas are created and tickit.ini is properly configured, yet, I get the above. Knowing where half this shit comes from may help me narrow stuff done and also give me an opportunity to fix anything hokey in my config (but, I've double checked everything multiple times and it still won't process).
In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.
Thank you. For as many years as I've known you, you are still a stand-up guy (with less hair than the last time I saw you). :)
Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 03:23 pm
If you still want to go the multiple configs route, you should now be able to pass a unique configuration filename on the command-line to tickit.js (e.g "?tickit fidotick.ini")
And then in within that configuration file, specify "echocfg=fidoecho.ini", and that would link that fidotick.ini to fidoecho.ini.
I performed a Git pull about an hour ago then saw this message. I made the necessary changes and here's the output:
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt DAILY Semaphore signaled for Timed Event: FIDO_TIC
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC Running timed event: FIDO_TIC
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC !JavaScript /sbbs/exec/load/fido_syscfg.js line 43: Error: 2 opening '/sbbs/ctrl/sbbsecho.ini'
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC Timed event: FIDO_TIC returned 0
In the file I called /sbbs/ctrl/fidonet_tick.ini, I added this on the first line:
EchoCfg=/sbbs/ctrl/fidonet.ini
Error 2 opening sbbsecho.ini.
Thoughts?
Are you psasing "fidonet_tick.ini" on the tickit.js command-line?
Ha! Yeah, it's been long time. You were the first person to purchase Synchronet (or first of very few to purchase the source code) as I recall. Do you still have that old source code?
On 01-30-21 14:35, Digital Man wrote to Dream Master <=-
Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) -
anyway, so I'm wondering if perhaps you're trying to solve a
non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding,
maybe no other SBBSecho users are also on WWIVnet (seems unlikely).
Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 04:48 pm
Are you psasing "fidonet_tick.ini" on the tickit.js command-line?
Sorry for the late reply but I've been busy with family stuff.
The SCFG configuration has the specific Timed Event as the following:
?tickit.js /sbbs/ctrl/fidonet_tick.ini
Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 04:44 pm
Ha! Yeah, it's been long time. You were the first person to purchase Synchronet (or first of very few to purchase the source code) as I recall. Do you still have that old source code?
I believe I was the first to purchase both. :)
No. When I moved from
Anaheim to Placentia, everything was put into boxes by my mother as I wasn't being very helpful in the move (you know, having a life). When I was going through the boxes, I tagged everything that was important. After leaving home and moving to Corona Hills (91 and Green Mountain), my mother put all the boxes up and then a couple years later my parents decided to clean out the garage. Guess where my "super duper really important box" was at? NOT THERE!
I don't think that would work as the code I wrote expected just the filename to be specified (e.g. "?tickit.js fidonet_tick.ini"). The ctrl directory is assumed.
I believe I was the first to purchase both. :)
That's pretty prestigious. :-)
Ah. :-( Well, at least I can restore the source code to you after all these years: https://gitlab.synchro.net/main/sbbs1a
Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 01:59 am
I believe I was the first to purchase both. :)
That's pretty prestigious. :-)
It was ironic how close you and I lived and whom we associated with. :)
Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)
Ah. :-( Well, at least I can restore the source code to you after all these years: https://gitlab.synchro.net/main/sbbs1a
I think I'll stick with SBBS3 instead of 1a. There's been a "few" improvements since then.
Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 01:58 am
I don't think that would work as the code I wrote expected just the filename to be specified (e.g. "?tickit.js fidonet_tick.ini"). The ctrl directory is assumed.
The last outstanding problem is binkit.js. binkit.js wants sbbsecho.ini instead of command line ini file.
It was ironic how close you and I lived and whom we associated with. :)
Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)
But seriously, thank you. Those early sales were my inspiration to keep going. If nobody else wanted to use the software, I'm sure I'd have lost interest long ago. But not many bought (or were offered) the source code back then either. I (like most software devs of the time) was overly-paranoid about protecting my "intelectual property". Seems silly in hindsight.
Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)
Ah, well that's a whole other conversation we probably shouldn't be having here. :-)
Ah, yeah, just a few. It was fun to get that old code compiling and working again (post Y2K and all), using those old tools. It all feels like a toy now: so few files, so few lines of code, so few dependencies. Piece of cake to find and fix bugs in, even without the use of a debugger.
Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)
whoa whoa whoa. TMI TMI
speak no further.
Okay ... I'm annoyed as I think I just fucked myself. :|
Time to consolidate all the files and start again. (I need an eye roller)
I'm trying to figure out why you want to add so much complexity to your setup. Back to the original issue, I have WWIVnet and many others with no echotag conflicts. All the WWIV echotags are prefixed with "WWIV_".
If its a filegate issue, I must admit I don't always subscribe to more then the nodelist filegates*, but I haven't had a problem there either. :-/
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 577 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 61:28:48 |
| Calls: | 10,734 |
| Calls today: | 1 |
| Files: | 5 |
| Messages: | 442,632 |