3 ms·

Holy shit, that is an incredible idea!

• WhyNotHugo 4y ago
  Here's a sample: https://git.sr.ht/~whynothugo/dotfiles/tree/c0bf9296c6ca8661f1eb9ee79e33606e6e88cc7c/item/home/.config/systemd/user/ssh-agent.service https://git.sr.ht/~whynothugo/dotfiles/tree/c0bf9296c6ca8661... Note that the ordering is important so that `SSH_AUTH_SOCK` is passed down to other services.
  • zaarn 4y ago
    You can order them using user targets. Ie, create a ssh-agent.target and have the default target depend on it. Now your ssh-agent is guaranteed to be online when the default target comes up.
    • georgyo 4y ago
      His method already does that. Creating a target for a single service is very much overkill. Though creating a target like setup or pre-default and putting in there might be a fine idea if you have other services you want to run that way. But, since the unit is already setting a fixed path for the agent, I would just put that path in my .profile and call it a day. Having systems do environment variable injection seems too fragile to me, especially for static variables.
      • WhyNotHugo 4y ago
        I mostly do the injection to keep EVERYTHING related to the agent in a single file. But yeah, `environment.d` or `.profile` would be simpler. I mostly opted to keep everything in one place.