Hiya gang...
Just updated my Pi with all the latest and greatest (v3.17a). While updating I saw LOTS of DNDEBUG statements which I am assuming is not an issue. In my bash at the end when it updates, I run jsexec update.js and get the following...
Installing SBBSLIST v4 (replacing SBl v3)
Synchronet BBS List v4(1.34)
Upgrading from: ../xtrn/sbl/sbl.dab
!@Error 2 opening ../xtrn/sbl/sbl.dab
Now at this point in time I only use the Pi's for SBBSECHO and am assuming being I haven't run ./sbbs none of the files needed for the upgrade have been created.
Am I correct in assuming this?
Also, in the future I want to run ./sbbs I should do a fresh install?
Digital Man wrote to Bill McGarrity on 01-30-18 16:43 <=-
Re: SBBSLIST v4 error
By: Bill McGarrity to All on Tue Jan 30 2018 10:25 am
Hiya gang...
Just updated my Pi with all the latest and greatest (v3.17a). While updating I saw LOTS of DNDEBUG statements which I am assuming is not an issue. In my bash at the end when it updates, I run jsexec update.js and get the following...
Installing SBBSLIST v4 (replacing SBl v3)
Synchronet BBS List v4(1.34)
Upgrading from: ../xtrn/sbl/sbl.dab
!@Error 2 opening ../xtrn/sbl/sbl.dab
Now at this point in time I only use the Pi's for SBBSECHO and am assuming being I haven't run ./sbbs none of the files needed for the upgrade have been created.
You can safely ignore that. It just means you (or anyone) never ran the SBL door on that system, which probably isn't that uncommon. I'll fix
that error in the upgrade process.
Am I correct in assuming this?
Also, in the future I want to run ./sbbs I should do a fresh install?
Not unless you want to for some specific reason. A fresh install
shouldn't be necessary.
Digital Man wrote to Bill McGarrity on 01-30-18 16:43 <=-
Re: SBBSLIST v4 error
By: Bill McGarrity to All on Tue Jan 30 2018 10:25 am
Hiya gang...
Just updated my Pi with all the latest and greatest (v3.17a). While updating I saw LOTS of DNDEBUG statements which I am assuming is not an issue. In my bash at the end when it updates, I run jsexec update.js and get the following...
Installing SBBSLIST v4 (replacing SBl v3)
Synchronet BBS List v4(1.34)
Upgrading from: ../xtrn/sbl/sbl.dab
!@Error 2 opening ../xtrn/sbl/sbl.dab
Now at this point in time I only use the Pi's for SBBSECHO and am assuming being I haven't run ./sbbs none of the files needed for the upgrade have been created.
You can safely ignore that. It just means you (or anyone) never ran the SBL door on that system, which probably isn't that uncommon. I'll fix that error in the upgrade process.
Great... figured that. :)
Should I run the SBL door using JSEXEC so it can create one?
Digital Man wrote to Bill McGarrity on 01-31-18 15:51 <=-
Re: SBBSLIST v4 error
By: Bill McGarrity to Digital Man on Wed Jan 31 2018 01:06 pm
Digital Man wrote to Bill McGarrity on 01-30-18 16:43 <=-
Re: SBBSLIST v4 error
By: Bill McGarrity to All on Tue Jan 30 2018 10:25 am
Should I run the SBL door using JSEXEC so it can create one?
When I say "SBL", I'm referring (usually) the old Synchronet BBS List
door (v1-v3), written in C and using a clumsy flat-file database (sbl.dab). Since it's a native program (not JavaScript), you can't
execute it using JSexec.
The new "SBBSLIST" (v4) replaces the old SBL. You don't need an SBL.DAB file. In fact I made changes to sbbslist.js to insure that. You should
be able to run sbbslist.js without any sbl.dab or sbbslist.json file.
The sbl.dab is not really *used* by sbbslist v4, it just supports upgrading from that old database (sbl.dab) to the new sbbslist.json, automagically, if needed.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,063 |
| Nodes: | 17 (0 / 17) |
| Uptime: | 34:46:42 |
| Calls: | 501,357 |
| Calls today: | 2 |
| Files: | 109,427 |
| D/L today: |
1,647 files (226M bytes) |
| Messages: | 302,460 |