Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Also great for running an SSH Agent, since they aren't coupled to some magic invocation in some bashrc but will always be started when the user session starts and cleanly terminated when you log out (or linger if you set that up)


Holy shit, that is an incredible idea!


Here's a sample:

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.


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.


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.


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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: