29.10.2024 10:03, Adam Nielsen wrote:
I tried using RequiresMountsFor=/mnt/share however again, if it runs too
early in the boot process the mount is not there and the unit fails to
start, and is not retried (logs just say "Job myservice.service/start
failed with result 'dependency'.")
Requires
On Tue, Oct 29, 2024 at 6:28 AM Phillip Susi wrote:
>
> So if you want to prevent automounting entirely you have to... open the
> disk device read only and take the bsd lock, and hold it until after
> closing the write file descriptor? Plus probably a little more time to
> give udev a chance to t
On Tue, 29 Oct 2024 at 15:00, Mantas Mikulėnas wrote:
> On Tue, Oct 29, 2024, 09:51 Henti Smith wrote:
>
>> On Mon, 28 Oct 2024 at 19:17, Mantas Mikulėnas wrote:
>>
>>> On Mon, Oct 28, 2024 at 8:54 PM Henti Smith
>>> wrote:
>>>
Where can I find detailed information on where to find the na
On Tue, Oct 29, 2024, 09:51 Henti Smith wrote:
> On Mon, 28 Oct 2024 at 19:17, Mantas Mikulėnas wrote:
>
>> On Mon, Oct 28, 2024 at 8:54 PM Henti Smith
>> wrote:
>>
>>> Where can I find detailed information on where to find the names when
>>> systemd-udevd sees the interface for the first time
Lennart Poettering writes:
> It prevents it fully. However, udev installs an inotify watch on all
> relevant block devices, which watches for IN_CLOSE_WRITE events, and
> then triggers the device again. IN_CLOSE_WRITE is the event that is
> generated when an inode is closed after it was open for
On Tue, 29 Oct 2024 at 02:50, Adam Nielsen wrote:
> Hi all,
>
> I'm having some problems getting a systemd unit to start during system
> boot. Can anyone advise what I'm doing wrong?
>
> The service starts fine if I run `systemctl start myservice`, the issue
> is that it fails to start during bo
On Mon, 28 Oct 2024 at 19:17, Mantas Mikulėnas wrote:
> On Mon, Oct 28, 2024 at 8:54 PM Henti Smith
> wrote:
>
>> Where can I find detailed information on where to find the names when
>> systemd-udevd sees the interface for the first time ?
>>
>
> At that point, they are just the original kernel
On Tue, Oct 29, 2024 at 4:50 AM Adam Nielsen wrote:
> Hi all,
>
> I'm having some problems getting a systemd unit to start during system
> boot. Can anyone advise what I'm doing wrong?
>
> The service starts fine if I run `systemctl start myservice`, the issue
> is that it fails to start during
On Mon, Oct 28, 2024 at 10:17 PM Mantas Mikulėnas wrote:
>
> For example, maybe:
> Property=DEVPATH=/devices/pci:00/:00:11.0/:06:00.0/net/eth*
Does Property accept wildcards? Manual does not mention it, only
selected directives are described as accepting "shell style globs".
> If n
> > I tried using RequiresMountsFor=/mnt/share however again, if it runs too
> > early in the boot process the mount is not there and the unit fails to
> > start, and is not retried (logs just say "Job myservice.service/start
> > failed with result 'dependency'.")
>
> RequiresMountsFor only works
10 matches
Mail list logo
