[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Mysterious ssh-agent session



While troubleshooting my ssh-agent setup, I discovered that an extra
ssh-agent instance was running, and I have no idea what is starting this.

What I want is to have ssh-agent run as a systemd user service
(following the instructions at
<https://wiki.archlinux.org/index.php?title=SSH_keys&oldid=571850#Start_ssh-agent_with_systemd_user>),
but the other instance is interfering.  Here is where it is in the
process tree (via htop):

 1756  ├─ /lib/systemd/systemd --user
31808  │  ├─ /usr/lib/flatpak/flatpak-session-helper
26143  │  ├─ /usr/lib/dconf/dconf-service
22233  │  ├─ /usr/bin/dunst
22204  │  ├─ /usr/lib/xdg-desktop-portal/xdg-desktop-portal-gtk
22187  │  ├─ /usr/lib/flatpak/xdg-permission-store
22184  │  ├─ /usr/lib/flatpak/xdg-document-portal
22180  │  ├─ /usr/lib/xdg-desktop-portal/xdg-desktop-portal
21243  │  ├─ /usr/bin/dirmngr --supervised
18747  │  ├─ /usr/lib/gvfs/gvfsd-trash [snip]
18672  │  ├─ /usr/lib/gvfs/gvfs-udisks2-volume-monitor
18534  │  ├─ /usr/lib/gvfs/gvfsd-metadata
 5759  │  ├─ /usr/bin/gpg-agent --supervised
 1934  │  ├─ /usr/lib/x86_64-linux-gnu/gconf/gconfd-2
 1856  │  ├─ /usr/lib/gvfs/gvfsd
 1849  │  ├─ /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
 1835  │  ├─ /usr/lib/at-spi2-core/at-spi-bus-launcher
 1847  │  │  └─ /usr/bin/dbus-daemon [snip]
 1790  │  ├─ /usr/bin/pulseaudio --start --log-target=syslog
 1932  │  │  └─ /usr/lib/x86_64-linux-gnu/pulse/gconf-helper
 1771  │  ├─ /usr/bin/dbus-daemon [snip]
 1762  │  ├─ /usr/bin/ssh-agent -t 2m -D -a /run/user/1000/ssh-agent.socket
 1761  │  ├─ /usr/bin/mpd --no-daemon
 1757  │  └─ (sd-pam)
 1763  │  │  └─ i3
 1876  │  │     ├─ /usr/bin/ssh-agent i3
 1833  │  │     ├─
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
 1832  │  │     └─ clipit

(The ssh-agent instance with PID 1762 is the one I want; PID 1876 is the
unwanted instance.)

I need to know how to either
  a) disable the instance started under "(sd-pam)", so I can use my
     systemd user service, or
  b) configure the instance started under "(sd-pam)", and use that
     instead of my system user service.

I am using lightdm to start X, and my session is the i3 WM.  In case
it's relevant, I also start
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 in my
~/.xsessionrc file.  I am running Debian 9.8 on x86_64.

Thanks,
Aidan Gauland

Reply to: