public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd - how to pre start nfs client services
Date: Sat, 31 Aug 2024 18:28:39 +0100	[thread overview]
Message-ID: <22409681.EfDdHjke4D@rogueboard> (raw)
In-Reply-To: <95d502c8-ea41-47a6-ac7d-8b0368722a05@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-08-31 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 14:32 [gentoo-user] systemd - how to pre start nfs client services Daniel Frey
2024-08-31 17:28 ` Michael [this message]
2024-09-01 18:43   ` Daniel Frey
2024-09-01 18:57   ` Daniel Frey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22409681.EfDdHjke4D@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox