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. >>> root@mollydew:/home/rlh# >> >> Well, that's weird. I installed approx on a Debian 12 machine, and got >> the same results you did. However: >> >> root@tsalmoth:~# ll /lib/systemd/system/approx* >> -rw-r--r-- 1 root root 165 Feb 12 2023 '/lib/systemd/system/approx@.service' >> -rw-r--r-- 1 root root 167 Feb 12 2023 /lib/systemd/system/approx.socket >> root@tsalmoth:~# systemctl status approx.service >> Unit approx.service could not be found. > > But here I cannot see approx.service, only approx@.service > (ie. service which can have multiple instances)
What if you issue: systemctl status "approx@*.service" KJ
