On Wed, 11 Sept 2024 at 12:51, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote:
On Wed, Sep 11, 2024 at 2:35 PM Henti Smith <henti@xxxxxxxxxxxxxxxxx> wrote:
>
> On Tue, 10 Sept 2024 at 18:11, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote:
>>
>> Because Requires without After is useless. I am yet to see the use case
>> for it.
>
>
> I don't follow. After adding Requires the config looks like:
>
> [Unit]
> Description=Mission Control
> After=network.target data.mount
> Wants=network.target
> Requires=data.mount
>
> So it has both After and Requires ?
>
Are you using a background NFS mount by default?
It is a data collection system and we're using a Google Transfer Appliance aka GTA (https://cloud.google.com/transfer-appliance/docs/4.0/overview) to write test data to. The system is used to collect data in the field by non technical people.
The process is currently:
* Power on the GTA (appliance exporting NFS share to /mnt/ta-data
* Power on the data collection device (Linux based on Ubuntu 20.04)
The GTA takes some time to start up and there is a start up procedure of starting the GTA and waiting 5 minutes before starting the data collection device, however I would like to remove people from the process completely.
What I'm trying to achieve:
* Data collection device boots up
* Mounts the NFS drive on /data
* Start the mission service once /data is mounted and available.
I hope this clarifies things.
Kind regards
Henti
