** Description changed:

  In new versions of openssh, it ships ssh-agent.service and ssh-
  agent.socket to be used as systemd user units. However, ssh-
  agent.service does not have an "Install" section, and it could not be
  enabled.
  
-     carbon roy ~ > systemctl --user enable --now ssh-agent.service
-     The unit files have no installation config (WantedBy=, RequiredBy=, 
UpheldBy=,
-     Also=, or Alias= settings in the [Install] section, and DefaultInstance= 
for
-     template units). This means they are not meant to be enabled or disabled 
using systemctl.
+     carbon roy ~ > systemctl --user enable --now ssh-agent.service
+     The unit files have no installation config (WantedBy=, RequiredBy=, 
UpheldBy=,
+     Also=, or Alias= settings in the [Install] section, and DefaultInstance= 
for
+     template units). This means they are not meant to be enabled or disabled 
using systemctl.
  
-     Possible reasons for having these kinds of units are:
-     • A unit may be statically enabled by being symlinked from another unit's
-       .wants/, .requires/, or .upholds/ directory.
-     • A unit's purpose may be to act as a helper for some other unit which has
-       a requirement dependency on it.
-     • A unit may be started when needed via activation (socket, path, timer,
-       D-Bus, udev, scripted systemctl call, ...).
-     • In case of template units, the unit is meant to be enabled with some
-       instance name specified.
+     Possible reasons for having these kinds of units are:
+     • A unit may be statically enabled by being symlinked from another unit's
+       .wants/, .requires/, or .upholds/ directory.
+     • A unit's purpose may be to act as a helper for some other unit which has
+       a requirement dependency on it.
+     • A unit may be started when needed via activation (socket, path, timer,
+       D-Bus, udev, scripted systemctl call, ...).
+     • In case of template units, the unit is meant to be enabled with some
+       instance name specified.
  
  The above is also true from debian upstream source code
  
  https://salsa.debian.org/ssh-
  team/openssh/-/blob/master/debian/systemd/ssh-
  agent.service?ref_type=heads
  
  Checking the ssh-agent service definition shipped by archlinux, theirs
- have the following which makes the symptom go away
+ has the following which makes the symptom go away
  
  ```
  [Install]
  Also=ssh-agent.socket
  ```

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154243

Title:
  ssh-agent.service could not be installed correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2154243/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to