On Tue, Apr 06, 2021 at 12:51:56PM +0100, Simon McVittie wrote:
> On Fri, 02 Apr 2021 at 20:54:05 +0300, Arseny Maslennikov wrote:
> > There's at least a use case to know if an active session owned by the
> > UID is present on seat X:
> > https://gitlab.gnome.org/GNOME/gvfs/-/issues/557
> > In shor
On Fri, 02 Apr 2021 at 20:54:05 +0300, Arseny Maslennikov wrote:
> There's at least a use case to know if an active session owned by the
> UID is present on seat X:
> https://gitlab.gnome.org/GNOME/gvfs/-/issues/557
> In short, if a USB storage drive is connected to a particular seat,
> we'd like t
On Fri, Apr 02, 2021 at 07:29:23PM +0300, Mantas Mikulėnas wrote:
> On Fri, Apr 2, 2021 at 7:17 PM Arseny Maslennikov
> wrote:
>
> > Hi everyone!
> >
> > Recently there's a trend for session-specific processes and services
> > (and even GUI apps, via `systemd-run --scope') to run as their own use
On Fri, Apr 2, 2021 at 7:17 PM Arseny Maslennikov
wrote:
> Hi everyone!
>
> Recently there's a trend for session-specific processes and services
> (and even GUI apps, via `systemd-run --scope') to run as their own user
> units on eligible systems/distros, to have a clean and controlled cgroup
> h
Hi everyone!
Recently there's a trend for session-specific processes and services
(and even GUI apps, via `systemd-run --scope') to run as their own user
units on eligible systems/distros, to have a clean and controlled cgroup
hierarchy.
I've been looking at https://systemd.io/DESKTOP_ENVIRONMENT
