Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runsvdir still needs to be started manually #2

Open
Earnestly opened this issue Jan 19, 2016 · 0 comments
Open

Runsvdir still needs to be started manually #2

Earnestly opened this issue Jan 19, 2016 · 0 comments

Comments

@Earnestly
Copy link
Owner

On my system runit's runsvdir has to be explicitly run after login as I've not managed to use systemd to start this as a per-user system service and would prefer to avoid adding this kind of logic to my shell's profile.

However if I cannot convince systemd to run this as a system service with User=%i instantiation I'll have to probably involve the login shell with something like:

if hash runsvdir 2> /dev/null && ! pgrep -U "$UID" -x runsvdir; then
    runsvdir "$LOCALDIR"/service &
fi

There's also the potential to use pam's pam_exec but that might involve even more wrappers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant