On 07/03/2015 01:22 PM, Lennart Poettering wrote:
B1;4002;0cOn Fri, 03.07.15 13:09, Francis Moreau (francis.m...@gmail.com)
wrote:
That's not an issue really. Since the device will not have any disk
label initially, and thus nothing will make use of it, until the
mke2fs is finished, and an
On Fri, 03.07.15 14:25, Francis Moreau (francis.m...@gmail.com) wrote:
But in the case of cryptsetup with 'tmp' option, the device can have a
disk label initially, since it's reformatted at each boot.
hmm, usually tmp is combined with a /dev/urandom key, and hence is
effectively empty
On 07/03/2015 11:08 AM, Lennart Poettering wrote:
On Tue, 30.06.15 17:37, Francis Moreau (francis.m...@gmail.com) wrote:
Hi,
I have a service 'A' which creates a device 'X' and does some
configuring of the device. The device is created in a 'ExecStart='
directive whereas its configuration
On Fri, 03.07.15 11:53, Francis Moreau (francis.m...@gmail.com) wrote:
On 07/03/2015 11:08 AM, Lennart Poettering wrote:
On Tue, 30.06.15 17:37, Francis Moreau (francis.m...@gmail.com) wrote:
Hi,
I have a service 'A' which creates a device 'X' and does some
configuring of the
On Tue, 30.06.15 17:37, Francis Moreau (francis.m...@gmail.com) wrote:
Hi,
I have a service 'A' which creates a device 'X' and does some
configuring of the device. The device is created in a 'ExecStart='
directive whereas its configuration happens during 'ExecStartPost='.
But it seems
On 07/03/2015 12:18 PM, Lennart Poettering wrote:
On Fri, 03.07.15 11:53, Francis Moreau (francis.m...@gmail.com) wrote:
On 07/03/2015 11:08 AM, Lennart Poettering wrote:
On Tue, 30.06.15 17:37, Francis Moreau (francis.m...@gmail.com) wrote:
Hi,
I have a service 'A' which creates a device
B1;4002;0cOn Fri, 03.07.15 13:09, Francis Moreau (francis.m...@gmail.com) wrote:
That's not an issue really. Since the device will not have any disk
label initially, and thus nothing will make use of it, until the
mke2fs is finished, and an ext2 label applied. When mke2fs then closes
the
On 06/30/2015 07:47 PM, Mantas Mikulėnas wrote:
Options:
- Configure it as part of ExecStart if possible.
I don't see how is this going to help, sorry.
- Configure it using a second .service unit (oneshot), and depend on
that one.
You meant all services that were depending on the device
Hi,
I have a service 'A' which creates a device 'X' and does some
configuring of the device. The device is created in a 'ExecStart='
directive whereas its configuration happens during 'ExecStartPost='.
But it seems that as soon as the device is seen by systemd, it creates
the corresponding
Options:
- Configure it as part of ExecStart if possible.
- Configure it using a second .service unit (oneshot), and depend on that
one.
- Do something with udev to mark unconfigured devices with SYSTEMD_READY=0?
Not sure how. But if you can do this, it'll directly affect the readiness
of the
10 matches
Mail list logo
