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.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbTUscACgkQseqq9sKV ZxnAlxAAzNrIiXcT9lOrBSuhl3VIcgS+imMAZVMbwcf9mD8A2C7hqEVGmoQUP0SJ Ysf7+xoiHBQJgu3n92q+SIfGQH6sI0M9N8+cWRSJJipQ4tsm/UacIx5gCWIKvj0m sfCIFNPdEjT2Aj/AX7acqnwjAQ+g36m178VLrMCoV6CBcatm5GBdY8UDD4paJGuF Br700vVIGP80yWZlvspY3V3PotAnio6vYSP+OkRMH8IZAr2g7cy2VRjDL9luL7F4 cQjjYks/snb7RqPctylGa3YL1q1XqpKyj+KHBw2W3he5avrYkxqKJt/mXSSgmEoh xux/KezWn3x2dOvaPsSrMVELpcua7cZCZ2U5WXG9VYeE4NF0GioC2wfvanjOaOoR jD9dUjeT++DAzifsaHqTfeOvXImHT4g8xKZHREdl+nHLP9HKOIg78XVoWRLPuYyl 1P1uGzGgaR5wXzqq8fwWIiOhKE5C6k4Tl9OMu9pbn/HIdVRrMO4IAxrWRhjEBPJ4 6bIznoWiYiEtTCxUcoxHWN3xi+FgOB9hyMs93bE6rESe16oqLG6OrbswB9kAygEf MjkCfJyu1oJ7TrE/OylxoijZF53UgnKilxIaGuiDY7CWFPzYZWgNA3tZ8y4RiQfZ epDzktG4FwqMewB68ndb/5vdEPoen4K8KISJo5L9ckYCGQrC+Bc=
=yHnu
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)