On Thu, 07 Dec 2023 09:27:08 +0100
Martin Steigerwald <martin@???> wrote:


> That is something I had a go at with my user-services approach quite
> a while ago. However I was not really entirely happy with the
> approach so I did not continue it. It was on Devuan's Gitlab, but I
> now just uploaded it to Gitea:
>
> https://git.devuan.org/martin/user-services
>
> Anyway, it worked well enough for running Pulseaudio and Redshift at
> the time it was not (yet) run automatically on systems with other
> init than Systemd, at least not within a KDE Plasma session.
>
> > For now I suggest you rely on something else to create the
> > link/enable the nested user-runsvdir on user login and remove the
> > link on user logout. For example many desktop have some "session
> > configure panel" to set components that are automatically started
> > with the desktop at login; you can run a script that creates the
> > link from there.
>
> Above approach just hooks into Plasma desktop startup, output from
> the install or upgrade script:
>
> > KDE Plasma desktop session detected. Installing user services
> > startup script to '~/.config/plasma-workspace/env'…
>
> So if you use something different you need to use a different
> approach. I bet what would always work is to stuff it into some shell
> startup file for the user session like '.bashrc' or '.zshrc'. In case
> you like to start something that depends on DBUS or SSH agent for
> example you need to make sure to add it after their environment
> variables are set up.
>
> > Not sure there is a proper way to run an action on logout..
> > None of the above looks satisfying to me but I'm afraid there is no
> > better way right now.
>
> Above user-services approach worked well enough for me. However… I
> still felt it was a bit hackish and was not entirely satisfied with
> it (see below). At the moment I do not need it, as Pulseaudio
> nowadays is started automatically. Also the functionality of redshift
> is integrated in Plasma nowadays.
>
> But anyway, maybe it is an approach that can work for you,
> Alexandros. It even had some primitive shell scripted usability
> boilerplate as explained in the markdown documentation.
>



Thank you for the reply . Not being a KDE user and having started now
to learn more at init systems i would prefer not to try user services
since it's for time being not implemented and logout is not handled if
i use .bashrc


Alexandros.