TZUTC: -0700
MSGID: 55102.sync@1:103/705 2d606e3d
REPLY: 55096.sync@1:103/705 2d604748
PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0
TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
  Re: Upgrading from v3.18 on CentOS7 to Ubuntu 25.04
  By: Jason to Digital Man on Thu Oct 23 2025 09:21 am

 >   Re: Upgrading from v3.18 on CentOS7 to Ubuntu 25.04
 >   By: Digital Man to Jason on Wed Oct 22 2025 10:01 pm
 >
 >  >  > I then do the /sbbs/exec/jsexec update and it doesn't seem to work.
 >
 >  > What makes you say that? Is the update.js current (the latest from the
 >  > Git repo)?
 >
 > I think this may be the problem, so im going to start over with the upgrade
 > and try this. Question, after i compile with symlinks, it appears that it's
 > symlinking the executables but not any of the .js files. Is this right?

Correct.

 > Did
 > i miss a step somewhere in the instructions? I would have thought it would
 > have moved this stuff over?

Step 4 from https://wiki.synchro.net/install:dev includes "download the daily
archive of the exec directory and extract into your Synchronet exec directory"
- I think you missed that.

 > Also, should it link the executables or create a symlink for the exec folder
 > over to the exec folder inside of the repo directory? This is where it gets
 > fuzzy for me because i'm not reading this in the instructions or im not
 > understanding it properly. I am dense at times, so it's probably me, but im
 > confused.. should i just move update.js script over by itself then?

It depends *how* you installed Synchronet to begin with. If you exec directory
itself is not already a symlink, then you'll need to recursively copy the *.js
files from the repo to your exec dir.

 > Also, the compile did create the symlinks for the update_to_v319 and
 > update_to_v320 but not one for update.js

That's correct. Compiling sbbs does nothing with scripts (e.g. *.js, *.src).

 >  > Look at the ctrl/main.ini file - does it have your BBS name, etc. in it?
 >  > If not, then there was no conversion of the your old ctrl/*.cnf files to
 >  > ctrl/*.ini, and if that's the case, then you ran
 >  > the wrong update.js or something like that.
 >
 > Here is a sample of the first few fields in the main.ini up to my system
 > password which i didn't copy here:
 >
 > Hard Drive CafeHDCBBSMontgomery, Alabama!!!!!!!!!!!!JasonThe Guru

Uh, that doesn't look right. The main.ini file should be .ini format, like so:

name=My BBS
qwk_id=MYBBS
location=My City, State
phonefmt=!!!!!!!!!!!!
operator=Sysop
guru=The Guru
etc.

 > What I am going to do is attempt to re-do the update on this new server,
 > manually copy over the new update.js file over to the /sbbs/exec directory
 > and then attempt to run that and see what I get. Maybe this will solve all
 > my issues.

You need to update *all* the .js (and other run-time files) in the exec dir,
not just update.js.

 > Still would like to know if i missed a step or something i didn't
 > read right. But as always thanks DM for your quick response! You've always
 > been great for me and I appreciate you!

Yeah, looks like Step 4 mentioned above was missed. No problem! Glad you're
upgrading to the latest release!
-- 
                                            digital man (rob)

Rush quote #40:
I can learn to resist, anything but temptation
Norco, CA WX: 61.2øF, 78.0% humidity, 3 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.30-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880
SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 266/512
SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58
SEEN-BY: 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426