ti 5. marrask. 2024 klo 14.55 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: > > ti 5. marrask. 2024 klo 14.48 Mark Hindley (m...@hindley.org.uk) kirjoitti: > > On Tue, Nov 05, 2024 at 02:36:36PM +0200, Martin-Éric Racine wrote: > > > > > It does rather feel that if-up.d/mountnfs should perhaps be updated > > > > > to > > > > > take account of this, rather than being a no-op. > > > > > > > > That would suggest reassigning this bug to src:initscripts, which > > > > provides that script. > > > > > > Adding the sysvinit maintainers to this thread for comment. > > > > Thanks for this. > > > > As I said to the OP in #1086710, my understanding is that the systemd > > maintainers don't want initscripts concurrently installed. Versions of > > systemd > > since 254.3-1 actually conflict with initscripts. > > > > I am not the right person to advise on issues on systemd systems. But I > > think > > the first step here is to purge initscripts and then see if the bad > > behaviour > > persists. I imagine it will then be easier to find the root of the problem. > > Thanks for this quick answer. > > My understanding also is that initscripts is not expected to get > installed on systemd hosts. > > What remains unclear (and could help OP) is to know how NFS shares are > expected to get mounted on systemd hosts that use DHCP (in this case, > via ifupdown).
This article seems to offer a solution: https://geraldonit.com/2023/02/25/auto-mount-nfs-share-using-systemd/ Martin-Éric
