systemd and BeeGFS client

[Steffen Grunewald]

Good morning,

I'd like to add BeeGFS to systemd's remote-fs.target, to ensure that some
subsequent services only start after BeeGFS has initialized the client
(since this may involve building the client module, the delay is large
and rather unpredictable, a "@reboot" crontab entry is inappropriate).

Without having to modify the remote-fs.target itself, is there a tested
approach for this?

With the current (7.4.6) unit file, the machine would connect to the batch
scheduler even before the filesystem is ready; this results in jobs being
assigned and failing. I'd like to avoid modifying the scheduler service's
unit file if possible, to keep changes limited and where they belong.

Any suggestions?

Thanks, S

--
Steffen Grunewald, Cluster Administrator
Max Planck Institute for Gravitational Physics (Albert Einstein Institute)
Am Mühlenberg 1 * D-14476 Potsdam-Golm * Germany
~~~
Fon: +49-331-567 7274
Mail: steffen.grunewald(at)aei.mpg.de
~~~

[Waltar]

If you define beegfs client for remote-fs.target and a module rebuild is necessary which could take time you may fail the target so it's not a good idea. 

As your batch scheduler depends on beegfs client up that is the real way to define this dependency eg with ".wants" dir with additional file inside so you don't need to manipulate the batch scheduler unit file itself for.