Re: [systemd-devel] sibling DNS lookup of nspawn containers

2021-06-18 Thread Johannes Ernst
> On Jun 18, 2021, at 16:02, Silvio Knizek wrote: > > Am Freitag, dem 18.06.2021 um 14:52 -0700 schrieb Johannes Ernst: >> >> Thanks, Silvio, but no luck: >> >> I have host, container a and container b. >> >> In both containers, .network for host0 has LLMNR=yes in the [Network] >> section >>

Re: [systemd-devel] sibling DNS lookup of nspawn containers

2021-06-18 Thread Silvio Knizek
Am Freitag, dem 18.06.2021 um 14:52 -0700 schrieb Johannes Ernst: > > Thanks, Silvio, but no luck: > > I have host, container a and container b. > > In both containers, .network for host0 has LLMNR=yes in the [Network] > section > > The host has LLMNR=yes in the [Resolve] section of >

[systemd-devel] UNSUSCRIBE

2021-06-18 Thread Saint Michael
UNSUSCRIBE ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] sibling DNS lookup of nspawn containers

2021-06-18 Thread Johannes Ernst
> On Jun 18, 2021, at 2:02, Silvio Knizek wrote: > > Am Donnerstag, dem 17.06.2021 um 20:26 -0700 schrieb Johannes Ernst: >> I’d like to be able to DNS lookup container b from within container a, if >> both were started with systemd-nspawn as siblings of each other, and shown >> as a and b in

Re: [systemd-devel] Reloading configuration after mount unit

2021-06-18 Thread Andrei Borzenkov
On 18.06.2021 20:48, Norbert Lange wrote: > Am Fr., 18. Juni 2021 um 16:35 Uhr schrieb Silvio Knizek > : >> >> Am Freitag, dem 18.06.2021 um 15:04 +0200 schrieb Norbert Lange: >>> Hello, >>> >>> I have an extra mount for /usr/local (Tools + Services which are just >>> useful for development),

Re: [systemd-devel] Reloading configuration after mount unit

2021-06-18 Thread Silvio Knizek
Am Freitag, dem 18.06.2021 um 19:48 +0200 schrieb Norbert Lange: > Am Fr., 18. Juni 2021 um 16:35 Uhr schrieb Silvio Knizek : > > > > Hi Norbert, > > > > make sure your /usr/local mount is done in the initrd and that you use > > »systemctl link /path/to/unit.service« to enable them. > That's not

Re: [systemd-devel] Reloading configuration after mount unit

2021-06-18 Thread Uoti Urpala
On Fri, 2021-06-18 at 19:48 +0200, Norbert Lange wrote: > If systemd assumes the whole /usr drive to be static and has no way to > dynamically reload and "retarget" > (adding new wants/requires dependencies to starting/started targets) > then I guess that's the end of it. Systemd does not

Re: [systemd-devel] Reloading configuration after mount unit

2021-06-18 Thread Norbert Lange
Am Fr., 18. Juni 2021 um 16:35 Uhr schrieb Silvio Knizek : > > Am Freitag, dem 18.06.2021 um 15:04 +0200 schrieb Norbert Lange: > > Hello, > > > > I have an extra mount for /usr/local (Tools + Services which are just > > useful for development), classically done vie /etc/fstab. > > > > Now there

Re: [systemd-devel] Alias for SMTP providers [ie. mutually exclusive service alternatives]

2021-06-18 Thread Cristian Rodríguez
On Tue, Jun 15, 2021 at 5:13 AM Kenneth Porter wrote: > > What happens if I list multiple services in a Wants= and After= clause that > are mutually exclusive (eg. sendmail/postfix/exim? How can I say "This unit > needs to send mail" without knowing which is enabled? Unfortunately "need to send

Re: [systemd-devel] Reloading configuration after mount unit

2021-06-18 Thread Silvio Knizek
Am Freitag, dem 18.06.2021 um 15:04 +0200 schrieb Norbert Lange: > Hello, > > I have an extra mount for /usr/local (Tools + Services which are just > useful for development), classically done vie /etc/fstab. > > Now there are a few systemd services within /usr/local/lib and systemd > does not seem

[systemd-devel] Reloading configuration after mount unit

2021-06-18 Thread Norbert Lange
Hello, I have an extra mount for /usr/local (Tools + Services which are just useful for development), classically done vie /etc/fstab. Now there are a few systemd services within /usr/local/lib and systemd does not seem to load/reload those and start the ones that add a sysinit.wants. currently

Re: [systemd-devel] sibling DNS lookup of nspawn containers

2021-06-18 Thread Silvio Knizek
Am Donnerstag, dem 17.06.2021 um 20:26 -0700 schrieb Johannes Ernst: > I’d like to be able to DNS lookup container b from within container a, if > both were started with systemd-nspawn as siblings of each other, and shown as > a and b in machinectl list. > > man nss-mymachines specifically notes