Skip to content

Runsvdir still needs to be started manually #2

@Earnestly

Description

@Earnestly

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions