Re: [systemd-devel] Starting service conditionally and retrying when failure

2017-10-04 Thread sdrb
Mantas Mikulėnas wrote: On Thu, Oct 5, 2017 at 7:51 AM, sdrb mailto:[email protected]>> wrote: Hi, I'd like to ask how to achieve following functionality in systemd: I'd like to start alsa-restore.service only once just after one of the specified files appears. Those file matches: /

Re: [systemd-devel] Starting service conditionally and retrying when failure

2017-10-04 Thread Mantas Mikulėnas
On Thu, Oct 5, 2017 at 7:51 AM, sdrb wrote: > Hi, > > I'd like to ask how to achieve following functionality in systemd: > > I'd like to start alsa-restore.service only once just after one of the > specified files appears. Those file matches: /dev/snd/control*. > > For now I have something like t

Re: [systemd-devel] Starting service conditionally and retrying when failure

2017-10-04 Thread Michael Chapman
On Thu, 5 Oct 2017, Camilo Aguilar wrote: you need to active your service unit when your files show up by monitoring the path using an additional path unit: https://www.freedesktop.org/software/systemd/man/systemd.path.html Anpother approach would be to have the unit get triggered by the device

Re: [systemd-devel] Starting service conditionally and retrying when failure

2017-10-04 Thread Camilo Aguilar
you need to active your service unit when your files show up by monitoring the path using an additional path unit: https://www.freedesktop.org/software/systemd/man/systemd.path.html On Thu, Oct 5, 2017 at 12:59 AM sdrb wrote: > Hi, > > I'd like to ask how to achieve following functionality in sy

[systemd-devel] Starting service conditionally and retrying when failure

2017-10-04 Thread sdrb
Hi, I'd like to ask how to achieve following functionality in systemd: I'd like to start alsa-restore.service only once just after one of the specified files appears. Those file matches: /dev/snd/control*. For now I have something like this: [Unit] Description=Save/Restore Sound Card State C

Re: [systemd-devel] systemd-nspawn/machinectl with LUKS/LVM

2017-10-04 Thread Mourad De Clerck
On 04/10/17 13:09, Lennart Poettering wrote: > Ah, uh, I forgot that your image is a block device. We are missing > some support there for that. /var/lib/machines may only contain > dirs/subvols and raw files right now, we don't support block > devices. But adding support for that should be easy, t

Re: [systemd-devel] systemd-nspawn/machinectl with LUKS/LVM

2017-10-04 Thread Lennart Poettering
On Mi, 04.10.17 12:41, Mourad De Clerck ([email protected]) wrote: > On 04/10/17 11:31, Lennart Poettering wrote: > > The image dissection logic can deal with either. The GPT approach is a > > bit nicer I think since the root partition can be marked as such, and > > > All right, makes sen

Re: [systemd-devel] systemd-nspawn/machinectl with LUKS/LVM

2017-10-04 Thread Mourad De Clerck
On 04/10/17 11:31, Lennart Poettering wrote: > The image dissection logic can deal with either. The GPT approach is a > bit nicer I think since the root partition can be marked as such, and All right, makes sense. >> 2) machinectl list-images doesn't detect the images in LVs; am I >> supposed to

Re: [systemd-devel] systemd-nspawn/machinectl with LUKS/LVM

2017-10-04 Thread Lennart Poettering
On Di, 03.10.17 17:04, [email protected] ([email protected]) wrote: > Hi, > > I'm trying to figure out the right way of using an LUKS-encrypted LV > with systemd-nspawn. > > I've got an LV called "containername" which is LUKS-encrypted, and I > start the container using: > > syst