You are not logged in.
Does anyone know why the /etc/idmapd.conf file is saved as a .pacsave file during the nfs-utils package update from testing today leaving no original file? For an existing working nfs system I would have thought that the original conf file would have been left intact and perhaps a .pacnew file created if necessary if the existing file is different from the default?
Pacman gives the following during update:
warning: /etc/idmapd.conf saved as /etc/idmapd.conf.pacsave
(4/5) upgrading nfs-utils [####################################] 100%I am guessing that there is a good reason for doing that but I could not see what the reason might be?
Last edited by mcloaked (2015-02-26 19:59:50)
Mike C
Offline
The thing is, there's no idmapd.conf shipped with nfs-utils anymore, thus, a .pacsave was created.
https://projects.archlinux.org/svntogit … 43702a3590
Offline
The thing is, there's no idmapd.conf shipped with nfs-utils anymore, thus, a .pacsave was created.
https://projects.archlinux.org/svntogit … 43702a3590
OK thank you for the link - if that is the rule when no conf file ships by default then a simple mv /etc/idmapd.conf.pacsave /etc/idmapd.conf will restore previous functionality. But I guess it is just important to pay attention during the pacman update! Or is the link you refer to suggesting that using idmapd.conf is no longer advised and instead swap to id_resolver.conf ?
Edit: I did some searching and found https://www.kernel.org/doc/Documentatio … mapper.txt so yes using idmapd.conf is legacy and using id_resolver.conf is current!
Last edited by mcloaked (2015-02-26 19:51:30)
Mike C
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Done!
Mike C
Offline