> False. It is documented in the manpage,
I looked in the manpage for my install, and no mention of socket
activation.
I looked in the README.Debian, and it indicated you can switch to socket
activation, over standard daemonization, if you choose, by masking sshd,
and enabling sshd.socket, and
> Socket activation provides a smoother (runtime) UX for users
SSHD configuration is not a user issue, but a systems administration
issue. A smoother UX for system administrators is a) Fully documented
solutions, or b) One source of truth for all things regarding a service,
hence the push for
> The point is to reduce footprint for greater density in production
environments. Most instances don't need an ssh daemon running all the
time.
If the point is to increase density, then sshd should just be off, and
not automatically started, unless it's required for work.
People install
I think a better option is to just not create a socket file for openssh,
as it's not required. OpenSSH server is fully capable of managing it's
own configuration via a very comprehensive config file, which is
universally applicable across various distros and other OSs.
Its just wholly unrequired
I ran this from a container image running under LXC, so perhaps that's
the confusion of jammy vs kinetic.
Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.15.53-1-pve x86_64)
(From motd)
While yes, this "solution" I did will in fact get wiped on upgrade, it
was done as a troubleshooting step, to
Public bug reported:
I am configuring OpenSSH to listen only on ipv4 and only on one
interface and one address, with nginx listening on 22 on the other
interface, and families.
In order to make this happen, I had to "break" the socket file installed
by the package at:
6 matches
Mail list logo
