chrisf Posted April 20, 2017 Share Posted April 20, 2017 I build a kernel last night because I wanted a headless debian based system, not the nightly desktop available for download. Everything went well (almost*) until I tried installing NFS Apr 21 09:16:39 tinker1 rpc.idmapd[7408]: main: fcntl(/run/rpc_pipefs/nfs): Invalid argument Apr 21 09:16:39 tinker1 nfs-common[7394]: Starting NFS common utilities: statd idmapd failed! Apr 21 09:16:39 tinker1 systemd[1]: nfs-common.service: control process exited, code=exited status=1 Apr 21 09:16:39 tinker1 systemd[1]: Failed to start LSB: NFS support files common to client and server. -- Subject: Unit nfs-common.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nfs-common.service has failed. -- -- The result is failed. Apr 21 09:16:39 tinker1 systemd[1]: Unit nfs-common.service entered failed state. A little googling leads me to believe dnotify is not enabled in the kernel... which was supposed to be replaced by inotify many years ago. Is this simply a config option in the kernel? If it is, can someone point me towards the way I go about enabling this? I've been building in the recommended Ubuntu 16.04 VM * almost... eth0 doesn't get an IPv4 address anymore since it's first boot. manually running dhclient after boot from the console works. Link to comment Share on other sites More sharing options...
Recommended Posts