> So, "Pipefs-Directory" is the culprit. I don't know when that > was set but it is obviously the reason for the issue.
Right. This was the previous default value, that was set in this file as shipped; so what's happened here is that you have a non-default 'Domain' setting, and on upgrade the package tried (and failed) to auto- merge the changes from the new version of the config file. On upgrade (with the default settings) you will have received a prompt asking you what to do with this file, and ultimately you appear to have chosen to keep the original version of the file. So I think we want some additional upgrade handling to forcibly change the Pipefs-Directory setting, since this is going to be a common merge failure. The blkmapd change is correct in its own right, but definitely unrelated to idmapd; we don't start blkmapd, and idmapd doesn't invoke this code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791588 Title: no idmapd for nfs4-clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/791588/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
