[systemd-devel] Session-specific user services

2021-04-02 Thread Arseny Maslennikov
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

Re: [systemd-devel] Session-specific user services

2021-04-02 Thread Arseny Maslennikov
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-

Re: [systemd-devel] Session-specific user services

2021-04-06 Thread Arseny Maslennikov
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/GN

Re: [systemd-devel] Environment variables are not sanitized when a graphical session dies

2021-04-06 Thread Arseny Maslennikov
On Fri, Apr 02, 2021 at 07:29:23PM +0300, Mantas Mikulėnas wrote: > one answer. (Note that stuff like $DISPLAY gets imported into systemd > --user's environment, to make it available to the services' > environment, and you can't make $DISPLAY have two values at once.) Oh. There's a design problem

Re: [systemd-devel] masking --global, but allowing --user

2021-09-18 Thread Arseny Maslennikov
On Fri, Sep 17, 2021 at 07:02:14PM -0500, Matt Zagrabelny wrote: > Greetings, > > I believe the Debian package of mpd enables a --global .service and > .socket unit for the mpd daemon/service. > > I'd like to mask that and install it just to a single --user service. > > I've tried that: > >

Re: [systemd-devel] logind: discontinuous TTYs?

2022-08-26 Thread Arseny Maslennikov
On Fri, Aug 26, 2022 at 06:55:46PM +0300, Toomas Rosin wrote: > Hi, > > I would like to configure logind so that it spawns getties only on tty1 > and tty12. I know I can set NAutoVTs to 12, but how to disable getties > on tty2..tty11? $ TTYID=tty2 # for example $ ln -s /dev/null

Re: [systemd-devel] Getting delegated IPv6 prefix from systemd-networkd

2022-10-23 Thread Arseny Maslennikov
On Sun, Oct 23, 2022 at 09:30:16AM +0300, Topi Miettinen wrote: > On 22.10.2022 15.55, Ian Pilcher wrote: > > On 10/19/22 17:05, Ian Pilcher wrote: > > > (I know that systemd-networkd can allocate subnets from the delegated > > > prefix to local interfaces, but that's not what I need to do in this

Re: [systemd-devel] Is there a way to find out if Delegate=yes?

2022-10-24 Thread Arseny Maslennikov
On Mon, Oct 24, 2022 at 06:07:39PM +0300, Yuri Kanivetsky wrote: > Hi, > > I'm experimenting with LXC containers: > > https://linuxcontainers.org/lxc/getting-started/ > > And there's a command I don't fully understand: > > systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- >

Re: [systemd-devel] Is there a way to find out if Delegate=yes?

2022-10-27 Thread Arseny Maslennikov
On Thu, Oct 27, 2022 at 11:48:20AM +0300, Yuri Kanivetsky wrote: > Arseny Maslennikov, for some reason I didn't receive your email. It had successfully reached this mailing list by 2022-Oct-25, so that means you're not subscribed to the list. Strangely enough, the mail receiver rejects ema

Re: [systemd-devel] rc-local.service and its future in systemd?

2023-04-24 Thread Arseny Maslennikov
On Mon, Apr 24, 2023 at 01:20:09PM +0300, Aki Ketolainen wrote: > > as Lennart already told you in the GitHub issue that "last" just doesn't > > make sense in systemd, there is also no need to change the dependencies > > global for everyone. Especially as there are systems out there which > >

Re: [systemd-devel] Query on sshd.socket sshd.service approaches

2024-03-06 Thread Arseny Maslennikov
On Wed, Mar 06, 2024 at 09:31:52AM +0100, Lennart Poettering wrote: > On Mi, 06.03.24 11:11, Shreenidhi Shedi (shreenidhi.sh...@broadcom.com) wrote: > > > Hi All, > > > > What is the rationale behind using sshd.socket other than not keeping sshd > > daemon running always and reducing memory