Re: approx in debian 12

From	Charles Curley <charlescurley@charlescurley.com>
Newsgroups	linux.debian.user
Subject	Re: approx in debian 12
Date	2023-11-16 18:30 +0100
Message-ID	<HAOlH-5SMP-1@gated-at.bofh.it> (permalink)
References	<HADJD-5LSh-5@gated-at.bofh.it> <HADJD-5LSh-7@gated-at.bofh.it> <HADJD-5LSh-9@gated-at.bofh.it> <HADJD-5LSh-11@gated-at.bofh.it> <HADJD-5LSh-3@gated-at.bofh.it>
Organization	occasionally

Show all headers | View raw

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/

Thread

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

csiph-web