On Thu 2025-05-08 22:32:11 +0100, Colin Watson wrote:
> I think After= is unnecessary. systemd.socket(5) says (bearing in mind
> that Before= and After= are inverses, as one might expect from their
> names):
>
>Socket units automatically gain a Before= dependency on the service
>units t
> We can do this with the following patch to the OpenSSH package's
> ssh-agent.service file:
>
> diff --git a/debian/systemd/ssh-agent.service
> b/debian/systemd/ssh-agent.service index 72e0a3e46..19ea47c91 100644
> --- a/debian/systemd/ssh-agent.service
> +++ b/debian/systemd/ssh-agent.service
>
On Thu, May 08, 2025 at 04:40:22PM -0400, Daniel Kahn Gillmor wrote:
To fix this use case, we just need to tell systemd that any manual
attempt to start the ssh-agent service needs to ensure that the socket
is listening first.
We can do this with the following patch to the OpenSSH package's
ssh-
Control: tags 1103522 + patch
Ah, thanks, i think i understand what is going on now! I was able to
replicate the problem.
> Here is what I did to disable my non-systemd-managed agent and run it again
> through systemd:
> killall ssh-agent
> systemctl --enable ssh-agent.service ssh-agent.socket
>
> >> If your output looks the same as above, can you share the output of:
> >>
> >> systemctl --user status ssh-agent.socket ssh-agent.service
> >>
> >> That would let me see what your local process supervisor believes is
> >> going on with this service.
> >
> > ○ ssh-agent.socket - OpenSSH
Hi Antoine--
On Thu 2025-05-08 00:50:44 +0200, Antoine Le Gonidec wrote:
>> Can you share the output of the following command (run as your normal
>> user):
>>
>>systemctl --user cat ssh-agent.socket ssh-agent.service
>
> I get the exact same output as yours, no local overrides here.
great, t
> Can you share the output of the following command (run as your normal
> user):
>
>systemctl --user cat ssh-agent.socket ssh-agent.service
I get the exact same output as yours, no local overrides here.
> If your output looks the same as above, can you share the output of:
>
> systemctl
Hi Antoine--
On Fri 2025-04-18 16:26:36 +0200, Antoine Le Gonidec wrote:
> Since the 1:10.0p1-1 → 1:10.0p1-2 upgrade, the user socket for ssh-agent
> is no longer created in ${XDG_RUNTIME_DIR}/openssh_agent, but at an
> unpredictable path under /tmp.
Can you share the output of the following comm
On Fri, Apr 18, 2025 at 04:26:36PM +0200, Antoine Le Gonidec wrote:
Since the 1:10.0p1-1 → 1:10.0p1-2 upgrade, the user socket for ssh-agent
is no longer created in ${XDG_RUNTIME_DIR}/openssh_agent, but at an
unpredictable path under /tmp.
As an example, here is what it currently uses on my syst
Package: openssh-client
Version: 1:10.0p1-2
Severity: important
Since the 1:10.0p1-1 → 1:10.0p1-2 upgrade, the user socket for ssh-agent
is no longer created in ${XDG_RUNTIME_DIR}/openssh_agent, but at an
unpredictable path under /tmp.
As an example, here is what it currently uses on my system:
/
10 matches
Mail list logo
