On Sun, Jan 02, 2022 at 09:25:49PM +0100, Thomas Liske wrote:
> Looks like a systemd/cgroup related change in bullseye, buster seems
> not to be affected.
That sounds correct, I had attributed this behavior to some ssh updates
in the past.
Greetings
Marc
--
-
Hi Marc,
On Sat, 2022-01-01 at 20:55 +0100, Marc Haber wrote:
> Sure:
> 1 [1/4996]mh@torres:~ $ pgrep ssh
> 315675
> 315738
> [2/4997]mh@torres:~ $ sudo cat /proc/315675/cgroup
> [sudo] password for mh on torres:
> 0::/user.slice/user-1001.slice/session-296.scope
> [3/4998]mh@torres:~ $ sudo cat
Hi Thomas,
On Sat, Jan 01, 2022 at 02:31:04PM +0100, Thomas Liske wrote:
> could you please provide the content of /proc/$PID/cgroup for an socket
> activated sshd instance?
Sure:
1 [1/4996]mh@torres:~ $ pgrep ssh
315675
315738
[2/4997]mh@torres:~ $ sudo cat /proc/315675/cgroup
[sudo] password fo
Hi Marc,
could you please provide the content of /proc/$PID/cgroup for an socket
activated sshd instance?
As a workaround you might blacklist sshd in needrestart but I think a
generic approach handling socket activation services in needrestart
would be better. Therefore needrestart need a way to
Package: needrestart
Version: 3.5-5
Severity: normal
Hi,
when using ssh as a socket activated service (systemctl stop/disable
ssh.service, systemctl enable/start ssh.socket), after a library update
needrestart will offer to restart ssh.service. This fails since port 22
is occupied by the instance
5 matches
Mail list logo
