Re: [systemd-devel] elegant way to use a single mount unit file for multiple paths

2020-01-26 Thread Jérémy ROSEN
You can't use templates with .mount units because .mount units need to be named exactly after their mount point. That's probably not explicitly documented, but might be a good idea to add. For your use-case, I would probably use a generator (man systemd.generator) to solve that... It might not sol

[systemd-devel] Conditional dependency

2020-01-26 Thread prashantkumar dhotre
Hi, Is there a way to specify conditional dependency in service files ? My use case is : I have a include file my.include that contains 'After=core.service' among other things. I have services A,B,C and X. As of now , all include my.include. Now my requirement is - I want services A,B and C to be d

Re: [systemd-devel] making journald logs persistent on raspberry pi

2020-01-26 Thread Dave Howorth
On Fri, 24 Jan 2020 18:36:49 +0200 Mantas Mikulėnas wrote: > On Fri, Jan 24, 2020 at 5:32 PM Dave Howorth > wrote: > > > It's quite common on the Raspberry Pi to make /var/log a tmpfs, in > > order to reduce the number of writes to the SD card that is the pi's > > main storage. That's quite acce

[systemd-devel] systemd-resolved LLMNR keeps switching between ipv4 and ipv6

2020-01-26 Thread Георгий Кибардин
Hi, everybody! After switching to systemd-resolved I've discovered that local address resolution uses only LLMNR which causes some inconvenience. Resolving local network host names constantly jumps between ipv4 and ipv6. It is something like 2 minutes ping resolves ipv4 address and 2 other minutes

Re: [systemd-devel] dbus activation service path

2020-01-26 Thread Damian Ivanov
Also not related to my question, but a dbus-broker behavior/bug that causes flatpak to misbehave: https://github.com/flatpak/flatpak/issues/3342 On Fri, Jan 24, 2020 at 11:27 PM Damian Ivanov wrote: > > Hello! > > Thank you for all the great work! > Can't wait to test systemd-homed. > > I also ha

[systemd-devel] detect_container() for recent(?) docker

2020-01-26 Thread Matwey V. Kornilov
Hello, I've just found that an assumption used inside detect_container() is not always true, and that leads to virtualization misdetection. Namely, I am running systemd inside docker (19.03.5) container on ubuntu (18.04.2 kernel version is 4.15.0-45-generic). /* Interestingly /proc/1/sche