'Twas brillig, and Olivier Blin at 13/06/12 23:28 did gyre and gimble: > Colin Guthrie <[email protected]> writes: > >> 'Twas brillig, and Guillaume Rousse at 12/06/12 07:26 did gyre and gimble: >>> Le 12/06/2012 02:37, JA Magallón a écrit : >>>> On 06/12/2012 02:29 AM, JA Magallón wrote: >>>>> On 06/11/2012 10:22 PM, guillomovitch wrote: >>>>>> Name : nfs-utils Relocations: (not >>>>>> relocatable) >>>>>> Version : 1.2.6 Vendor: Mageia.Org >>>>>> Release : 2.mga3 Build Date: Mon Jun 11 >>>>>> 22:21:14 2012 >>>>>> Install Date: (not installed) Build Host: >>>>>> ecosse.mageia.org >>>>>> Group : Networking/Other Source RPM: (none) >>>>>> Size : 787418 License: GPL >>>>>> Signature : (none) >>>>>> Packager : guillomovitch <guillomovitch> >>>>>> URL : http://sourceforge.net/projects/nfs/ >>>>>> Summary : The utilities for Linux NFS server >>>>>> Description : >>>>>> This package provides various programs needed for NFS support on >>>>>> server. >>>>>> >>>>>> guillomovitch <guillomovitch> 1:1.2.6-2.mga3: >>>>>> + Revision: 259882 >>>>>> - add exports.d directory >>>>>> - use /var/lib/nfs/statd for statd, instead of /var/lib/nfs, as in >>>>>> fedora >>>>>> - add modprobe config file to alias 'nfs4' to 'nfs' >>>>>> - add systemd support >>>>>> - drop sysinit support >>>>>> - merge client and server package, as per redhat setup >>>>>> >>>>> >>>>> Some weird things happen with this and systemd... >>>>> I had nfs server active. After update and reboot, I had no nfs server >>>>> running. >>>>> What do I have to add in systemd to get them working ? >>>>> I got it by: >>>>> systemctl enable nfs.target (still had no server...) >>>>> systemctl enable nfs-server.service >>>>> >>>>> Are those the correct top level units ? >>>>> >>>>> TIA >>>>> >>>> >>>> Ah, and after reboot systemd still shows nfs-common.service: >>>> >>>> werewolf:/etc/systemd# systemctl --all | grep nfs >>>> proc-fs-nfsd.mount loaded active mounted RPC Pipe File >>>> System >>>> nfs-common.service error inactive dead >>>> nfs-common.service >>>> nfs-idmap.service loaded active running NFSv4 ID-name >>>> mapping daemon >>>> nfs-mountd.service loaded active running NFS Mount Daemon >>>> nfs-rquotad.service loaded inactive dead NFS Remote Quota >>>> Server >>>> nfs-server.service loaded active exited NFS Server >>>> nfs.target loaded active active Network File >>>> System Server >>>> >>>> werewolf:/etc/systemd# systemctl status nfs-common.service >>>> nfs-common.service >>>> Loaded: error (Reason: No such file or directory) >>>> Active: inactive (dead) since Tue, 12 Jun 2012 01:30:45 +0200; 1h >>>> 5min ago >>> Same issue here. I think that's just another bogus output of systemctl >>> list-units --all output. >> >> This happens if it's referred to by another unit. i.e. as an After or a >> Before reference etc. It shows up wtthout a proper description and just >> the unit name. I think it would be better to put a generic "[Missing] in >> the description rather than the unit fragment name, but hey ho. Maybe >> this is done already in newer versions. > > Right, we have this in remote-fs-pre.target : > After=nfs-common.service
Yup, this was added to systemd as nfs-server package did not have native units. The correct thing is to ensure all the daemons are setup prior to remote-fs-pre.target. So the "correct" solution here is to put: Before=remote-fs-pre.target In the relevant nfs server units to ensure that NFS mount points are properly mounted at boot. See this bug for background (comment 6 in particular): https://bugs.mageia.org/show_bug.cgi?id=5890#c6 Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
