Re: [systemd-devel] user unit with delayed users homes mount - ?

On 14/10/2022 12:02, Andrei Borzenkov wrote: On Fri, Oct 14, 2022 at 12:59 PM lejeczek wrote: Hi guys. I'm on Centos 8 S with systemd 239. Users homes are mounted at later (latest?) stage off NFS so when such a user logs in then: -> $ systemctl --user status -l xyz.service Unit

Re: [systemd-devel] user unit with delayed users homes mount - ?

On Fri, Oct 14, 2022 at 2:48 PM lejeczek wrote: > > > > On 14/10/2022 12:02, Andrei Borzenkov wrote: > > On Fri, Oct 14, 2022 at 12:59 PM lejeczek wrote: > >> Hi guys. > >> > >> I'm on Centos 8 S with systemd 239. > >> Users homes are mounted at later (latest?) stage off NFS so when such a > >>

Re: [systemd-devel] user unit with delayed users homes mount - ?

Andrei Borzenkov wrote on 14/10/2022 12:56: On Fri, Oct 14, 2022 at 2:48 PM lejeczek wrote: Is it possible and if so then how, to make "systemd" account for such a "simple" case - where home dir is net mounted very late? Without knowing how exactly your home directories are mounted it is

[systemd-devel] user unit with delayed users homes mount - ?

Hi guys. I'm on Centos 8 S with systemd 239. Users homes are mounted at later (latest?) stage off NFS so when such a user logs in then: -> $ systemctl --user status -l xyz.service Unit xyz.service could not be found. -> $ systemctl --user daemon-reload -> $ systemctl --user status -l

Re: [systemd-devel] user unit with delayed users homes mount - ?

On Fri, Oct 14, 2022 at 12:59 PM lejeczek wrote: > > Hi guys. > > I'm on Centos 8 S with systemd 239. > Users homes are mounted at later (latest?) stage off NFS so when such a user > logs in then: > > -> $ systemctl --user status -l xyz.service > Unit xyz.service could not be found. > -> $

Re: [systemd-devel] Finding network interface name in different distro

Le ven. 14 oct. 2022 à 20:41, Etienne Champetier a écrit : > > Hi All, > > When changing distro or distro major versions, network interfaces' > names sometimes change. > For example on some Dell server running CentOS 7 the interface is > named em1 and running Alma 8 it's eno1. > > I'm looking for

[systemd-devel] systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

Hi, since the issue came up on the Debian bug tracker at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019147 , I figured I ask here: Am 04.09.22 um 18:40 schrieb Bernhard Übelacker: > > Package: systemd-container > Severity: wishlist > X-Debbugs-Cc: bernha...@mailbox.org > > > Dear

[systemd-devel] Finding network interface name in different distro

Hi All, When changing distro or distro major versions, network interfaces' names sometimes change. For example on some Dell server running CentOS 7 the interface is named em1 and running Alma 8 it's eno1. I'm looking for a way to find the new interface name in advance without booting the new OS.