BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] new ssh error
- Subject: [Discuss] new ssh error
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Tue, 2 Jul 2024 16:24:27 -0400
- In-reply-to: <bb51baf8-2ab3-4320-8f6e-3f75541ada10@borg.org>
- References: <bb51baf8-2ab3-4320-8f6e-3f75541ada10@borg.org>
On Mon, 1 Jul 2024 13:53:17 -0700 Kent Borg <kentborg at borg.org> wrote: > After an 'apt upgrade' of openssh I am getting an unnerving error: > > > root at la:/home/kentborg# dpkg-reconfigure openssh-server > > rescue-ssh.target is a disabled or a static unit not running, not > > starting it. > > ssh.socket is a disabled or a static unit not running, not starting > > it. > > I don't see anything useful in web searches. TL;DR: these are notices, not errors. socket units are, well, socket units. They're systemd's version of (x)inetd.conf. A static unit is a unit that lacks an install section. This is not a bug: many units don't need to auto-start at boot time. They are triggered by other events. -- \m/ (--) \m/
- Follow-Ups:
- [Discuss] new ssh error
- From: kentborg at borg.org (Kent Borg)
- [Discuss] new ssh error
- References:
- [Discuss] new ssh error
- From: kentborg at borg.org (Kent Borg)
- [Discuss] new ssh error
- Prev by Date: [Discuss] new ssh error
- Next by Date: [Discuss] new ssh error
- Previous by thread: [Discuss] new ssh error
- Next by thread: [Discuss] new ssh error
- Index(es):