Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263576 > unrolled thread
| Started by | Kamil Jońca <kjonca@o2.pl> |
|---|---|
| First post | 2023-11-16 07:10 +0100 |
| Last post | 2023-11-16 19:10 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: approx in debian 12 Kamil Jońca <kjonca@o2.pl> - 2023-11-16 07:10 +0100
Re: approx in debian 12 Charles Curley <charlescurley@charlescurley.com> - 2023-11-16 18:30 +0100
Re: approx in debian 12 Greg Wooledge <greg@wooledge.org> - 2023-11-16 19:10 +0100
| From | Kamil Jońca <kjonca@o2.pl> |
|---|---|
| Date | 2023-11-16 07:10 +0100 |
| Subject | Re: approx in debian 12 |
| Message-ID | <HADJD-5LSh-3@gated-at.bofh.it> |
Charles Curley <charlescurley@charlescurley.com> writes: > On Thu, 16 Nov 2023 04:11:37 +0000 > "Russell L. Harris" <russell@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) KJ
[toc] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2023-11-16 18:30 +0100 |
| Message-ID | <HAOlH-5SMP-1@gated-at.bofh.it> |
| In reply to | #263576 |
On Thu, 16 Nov 2023 06:53:16 +0100 Kamil Jońca <kjonca@o2.pl> wrote: > Charles Curley <charlescurley@charlescurley.com> writes: > > [...] > [...] > > > > 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) Multiple instances, eh? That's a part of systemd I know nothing about. On my test machine, while approx is enabled, I have no instances actually running, which leads me to think that systemd launches an instance of approx when a client knocks on its port, much like inetd. And that could easily lead to multiple instances. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-11-16 19:10 +0100 |
| Message-ID | <HAOYp-5Tkn-3@gated-at.bofh.it> |
| In reply to | #263598 |
On Thu, Nov 16, 2023 at 10:26:48AM -0700, Charles Curley wrote: > Multiple instances, eh? That's a part of systemd I know nothing about. > On my test machine, while approx is enabled, I have no instances > actually running, which leads me to think that systemd launches an > instance of approx when a client knocks on its port, much like inetd. > And that could easily lead to multiple instances. Yes. That's precisely what "socket activation" is -- an inetd-like feature built into systemd.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web