I just wanted to direct the attention of Synchronet sysops to exec/chksetup.js:
You can run this script from an OS command prompt using jsexec, like so: "jsexec chksetup"
It will report any common issues found with your Synchronet configuration and data. If you want more detailed output about discovered issues, you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
An ideal Synchronet setup will report "No issues discovered" when running chksetup.js
Digital wrote:
I just wanted to direct the attention of Synchronet sysops to exec/chksetup.js:
You can run this script from an OS command prompt using jsexec, like so: "jsexec chksetup"
It will report any common issues found with your Synchronet configuration and data. If you want more detailed output about discovered issues, you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
An ideal Synchronet setup will report "No issues discovered" when running chksetup.js
Interesting:
!User #16 has a disallowed password
How can a user enter a disallowed password if it's disallowed? I'm sure I didn't put any config in after they created their account. How would I check? It looks like they created their account through the HTTP interface, so maybe this is more an echicken thing?
Opening list file: /sbbs/data/sbbslist.json
!finger ?bbs:End Of The Line BBS@vert.synchro.net result: TypeError: finger_result.join is not a function
you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
Re: chksetup.js
By: Digital Man to All on Sat Jan 11 2020 14:50:59
you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
i'm not seeing any difference between no "-v" and with "-v"... i updated just a few days ago...
the only other thing is that mine always tell me that my sbbslist.json entry for my system is different than the one on vert... i suspect this may be due to my event which updates my entry... it is possibly being executed after the update is sent to vert... i'll have to look at that and see if that's the case... perhaps this particular check can be enhanced to show the actual differences between the two?
you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
i'm not seeing any difference between no "-v" and with "-v"... i updated
just a few days ago...
Depending on what issues are found, that's often the case.
the only other thing is that mine always tell me that my sbbslist.json
entry for my system is different than the one on vert... i suspect this
may be due to my event which updates my entry... it is possibly being
executed after the update is sent to vert... i'll have to look at that
and see if that's the case... perhaps this particular check can be
enhanced to show the actual differences between the two?
Perhaps, though, that's not a simple thing to do.
I just wanted to direct the attention of Synchronet sysops to exec/chksetup.js:
You can run this script from an OS command prompt using jsexec, like so: "jsexec chksetup"
It will report any common issues found with your Synchronet configuration and data. If you want more detailed output about discovered issues, you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
An ideal Synchronet setup will report "No issues discovered" when running chksetup.js
digital man
Synchronet/BBS Terminology Definition #12:
CBM = Commodore Business Machines
Norco, CA WX: 60.6�F, 59.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net
good tool! i have two issues:
i will verify if sbbslist are synced, but the "has a long tagline" how
to fix it?
El 11/1/20 a las 19:50, Digital Man escribió:
I just wanted to direct the attention of Synchronet sysops to exec/chksetup.js:
You can run this script from an OS command prompt using jsexec, like so: "jsexec chksetup"
It will report any common issues found with your Synchronet configuration and data. If you want more detailed output about discovered issues, you can increase the verbosity with the "-v" option ("jsexec chksetup -v").
An ideal Synchronet setup will report "No issues discovered" when running chksetup.js
good tool! i have two issues:
!QWK-networked sub (rtn_mysti) has a long tagline
!QWK-networked sub (rtn_sync) has a long tagline
!QWK-networked sub (rtn_ti) has a long tagline
!QWK-networked sub (rtn_cnet) has a long tagline
!279 msg sub-boards have QWKnet taglines exceeding 63 printed characters Invoking: check_fido_origlines
Invoking: check_bbs_list
Opening list file: /sbbs/data/sbbslist.json
!'Dock Sud BBS' BBS entry on vert.synchro.net is different than local Invoking: check_syncdata
Invoking: check_imsg_list
Invoking: check_dove_net
Invoking: check_sub_codes
Invoking: check_dir_codes
Invoking: check_xtrn_codes
Invoking: check_sockopts_ini
!2 issues discovered
/sbbs/exec/chksetup.js executed in 2.20 seconds
i will verify if sbbslist are synced, but the "has a long tagline" how
to fix it?
Re: Re: chksetup.js
By: Ragnarok to Digital Man on Mon Jan 13 2020 10:21:34
QWK<->FTNi will verify if sbbslist are synced, but the "has a long tagline" how to fix it?
shorten it? seems legit...
FWIW: i can't see it from here because i'm on the other side of the
gateway so your message here has your QWK origin line in it... but do you really need to list connection protocols and domains in your origin lines? they
are generally used to list just the system name and possibly city/country location...
El 13/1/20 a las 11:34, mark lewis escribió:
Re: Re: chksetup.js
By: Ragnarok to Digital Man on Mon Jan 13 2020 10:21:34
i will verify if sbbslist are synced, but the "has a long tagline" how to fix it?
shorten it? seems legit...QWK<->FTN
FWIW: i can't see it from here because i'm on the other side of the
gateway so your message here has your QWK origin line in it... but do you really need to list connection protocols and domains in your origin lines? they
are generally used to list just the system name and possibly city/country location...
Yeap i will change it, are the limit up to 80 characters? maybe scfg
must warning that limit.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 15:02:51 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,311 |