open https://gitlab.synchro.net/main/sbbs/-/issues/558

services.ini contains a single gopher entry; Archaic HTTP-like protocol[Gopher]Port=1170Command=gopherservice.jsHowever, starting up sbbs I get4/29 20:39:20 srvc 0029 !ERROR 13 binding Gopher socket to port 70: Permission denied4/29 20:39:20 srvc Gopher listening on socket :: port 70I'm not running setcap since valgrind doesn't like that.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/558#note_3531

Double-check everything or restart sbbs after updating services.ini?
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/558#note_3533

Works for me:`4/29 18:50:48 srvc Gopher listening on socket 0.0.0.0 port 1170 `
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/558#note_3534

ok. I found the issue, and it's yet again down these stupid links we have to create for git.If you're in /sbbs/exec and try to edit ../ctrl/services.ini then edits the version in /sbbs/repo/ctrl and not the actual /sbbs/ctrl.I originally edited in /sbbs/ctrl then changed /sbbs/exec to run sbbs, realized I needed to change the port for gopher so did vi ../ctrl/services.iniI still dislike this whole git workaround and this is another reason why.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/558
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Nigel Reed wrote to GitLab note in main/sbbs <=-

https://gitlab.synchro.net/main/sbbs/-/issues/558#note_3534

ok. I found the issue, and it's yet again down these stupid links
we have to create for git.If you're in /sbbs/exec and try to edit ../ctrl/services.ini then edits the version in /sbbs/repo/ctrl
and not the actual /sbbs/ctrl.I originally edited in /sbbs/ctrl
then changed /sbbs/exec to run sbbs, realized I needed to change
the port for gopher so did vi ../ctrl/services.iniI still dislike
this whole git workaround and this is another reason why.

Perhaps consider NOT using symlinks? I don't use them, it's not like
disk space is an issue these days. Much easier to manage, IMHO.



... All the easy problems have been solved.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)

https://gitlab.synchro.net/main/sbbs/-/issues/558#note_3541

You don't have to have symlinks to the repo. I'm using Synchronet without symlinks.There's also a note [on the wiki](http://wiki.synchro.net/install:nix) about building Synchronet without symbolic links (In the 'Updating' section, refer to point 2 where it says " Rebuild Synchronet (replace symlinks with install if you prefer to copy executable and library files to your exec directory)"). I'm running Synchronet without symlinks to the repo and haven't had a problem.I normally use a software repository as a software development tool for keeping track of file revisions, so I normally try to avoid running software from a repository or keeping links to a repo, etc. for the reason you describe.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)