Hi. On Thu, Nov 16, 2023 at 07:02:39AM +0000, Russell L. Harris wrote: > On Thu, Nov 16, 2023 at 07:14:04AM +0100, Kamil Jo?ca wrote: > > Kamil Jo?ca <kjo...@o2.pl> writes: > > > > > Charles Curley <charlescur...@charlescurley.com> writes: > > > > > > > On Thu, 16 Nov 2023 04:11:37 +0000 > > > > "Russell L. Harris" <russ...@rlharris.org> wrote: > > > > > > > > > root@mollydew:/home/rlh# systemctl daemon-reload > > > > > root@mollydew:/home/rlh# systemctl restart approx > > > > > Failed to restart approx.service: Unit approx.service not found. > > > > > root@mollydew:/home/rlh# systemctl status approx > > > > > Unit approx.service could not be found.
It's expected, see below. > > What if you issue: > > systemctl status "approx@*.service" > > It appears to run; no error message is produced, but no output, either. > > But I am in not in familiar territory. What you have is approx.socket unit, which causes systemd to listen on tcp:9999. On each incoming connection "approx@<local-ip>:<local-port>-<remote-ip>:<remote-port>.service" is started. That service is only used to serve that particular connection, and is terminated after. Thus, there's nothing to restart. You just edit /etc/approx/approx.conf, and try your changes immediately. Reco
