On 5/11/19 4:40 AM, Martin Steigerwald wrote:
> Martin Steigerwald - 11.05.19, 11:26:
>> Hi.
>>
>> Now that the proof of concept is out, I am thinking about extending it
>> a little bit.
>>
>> - make is a package
>> - make "install-or-update.sh" into "/usr/bin/userservices" with the
>> following actions:
>> - install: Sets up userservices for the user
>> - update: Updates it
>> - remove: Removes i
>
> - remove: Removes user services from user directory completely (after
> confirmation)
>
Martin, et al.,

I think it was Steve who brought up the idea that there are different
places to enable user services, and I'd like to posit there are at least
two different kinds of user services:

* per-user (for all sessions)
* per-session

On my machine I use runit to start a per-user tor and per-use privoxy;
all my sessions share those services. On a per-session basis I see
things like pulseaudio (if you use it), ssh-agent, gpg-agent, screen
locker, and other services that you would shut down when a session closes.

You can start the per-user services either in /etc/services (with runit
strting runsvdir) or as a lazy-instantiation per user on first login.
These serives would persist and be shared across user sessions.

You can start per-session services in .xsession or .xinitrc, or .bashrc
and .bash_logout.

So I would recommend thinking about having two sets of services,
per-user and per-session, and perhaps having "uservice --user" and
"uservice --session" to manage each different kind.