Re: [gentoo-user] systemd - how to pre start nfs client services

[Daniel Frey <djqfrey@gmail.com>]

On 8/31/24 10:28, Michael wrote:
> On Saturday, 31 August 2024 15:32:38 BST Daniel Frey wrote:
>> I have a few frontends on TVs and use automount on some NFS sources.
>>
>> However, I can't seem find a way to start the nfs client services on
>> startup. Wiki for NFS and other documentation says that systemd does
>> this automatically (and it does) but I'm trying to eliminate a delay.
>>
>> The frontend start up and when you go to the screen that scans the
>> folder, it takes 5-10 seconds for systemd to start these services and
>> mount the NFS locations.
>>
>> On openrc this is simple and it takes less than a second at that screen.
>>
>> It is not waiting for a network, as on startup the interface connects to
>> a database and this part is working fine (it would be blank if it
>> started with no network.)
>>
>> Dan
> 
> Does 'systemd-analyze blame' show which service component causes the delay(s)?
> If the same service dependency occurs on both systems then it ought to take
> the same time to automount an exported directory.  This points to some systemd
> specific  service dependency/hierarchy causing the delay - as long as all
> other configuration variables remain the same.

That's a handy command, thanks.

According to the output:

10.097s storage-nas.mount
  4.550s systemd-networkd-wait-online.service

It's waiting for the automount. The wait-online completes, the UI 
immediately starts, and then I went to browse the catalog, and it takes 
about 6 seconds to start the services and then mount it.

I just want to have the needed NFS services started during startup, 
instead of waiting for someone to browse the library/files.

This is easy to do in openrc with the nfs-client service, but no such 
service unit exists with systemd as far as I can tell.

Dan