Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Thomas HUMMEL
On 2/7/24 19:55, Andrei Borzenkov wrote: You can add drop-in to either unit (and add generator to do it automatically), but I do not quite see what is it going to buy you. Hello, thanks for your answer and sorry for the previous confusions I made. What do you call generator here ? A custom

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Andrei Borzenkov
On 07.02.2024 19:20, Thomas HUMMEL wrote: On 2/7/24 11:50, Thomas HUMMEL wrote: Still I cannot understand where the Requires= comes in remote-fs.target unit as doc for special target only describes a Wants= dep added by systemd-fstab-generator in the case of auto mounts. Well, forget about

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Andrei Borzenkov
On 07.02.2024 13:50, Thomas HUMMEL wrote: Still I cannot understand where the Requires= comes in remote-fs.target unit It is generated by systemd-fstab-generator as doc for special target only describes a Wants= dep added by systemd-fstab-generator in the case of auto mounts. If doc for s

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Thomas HUMMEL
On 2/7/24 11:50, Thomas HUMMEL wrote: Still I cannot understand where the Requires= comes in remote-fs.target unit as doc for special target only describes a Wants= dep added by systemd-fstab-generator in the case of auto mounts. Well, forget about that Wants= dep which is to the mount uni

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Thomas HUMMEL
On 2/6/24 17:06, Silvio Knizek wrote: Hi Thomas, RequiresMountsFor=3D should be your friend. It just takes a space- separated list of paths and does all the other stuff by itself. Hello, thanks for your reply. Actually RequiresMountsFor is not what I need because I'd have to point some fi

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-06 Thread Demi Marie Obenour
On Tue, Feb 06, 2024 at 05:06:02PM +0100, Silvio Knizek wrote: > Am Dienstag, dem 06.02.2024 um 16:15 +0100 schrieb Thomas HUMMEL: > > Hello, > >=20 > > I'm using systemd-239-74 on RHEL 8.8 EUS. > >=20 > > I was wondering if one can express the following : > >=20 > > start some service *only and on

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-06 Thread Silvio Knizek
Am Dienstag, dem 06.02.2024 um 16:15 +0100 schrieb Thomas HUMMEL: > Hello, >=20 > I'm using systemd-239-74 on RHEL 8.8 EUS. >=20 > I was wondering if one can express the following : >=20 > start some service *only and only if/when* all remote mounts (ex: nfs,= =20 > some parallel fs) has *succeeded

[systemd-devel] Submitting a service activation to remote mounts success

2024-02-06 Thread Thomas HUMMEL
Hello, I'm using systemd-239-74 on RHEL 8.8 EUS. I was wondering if one can express the following : start some service *only and only if/when* all remote mounts (ex: nfs, some parallel fs) has *succeeded*, taking into account it may take some time for some mount (some fs clients just live cur