![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1204929 https://bugzilla.suse.com/show_bug.cgi?id=1204929#c12 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #12 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Thomas Blume from comment #11)
So, most probably the chown shouldn't be necessary.
I case of:
https://bugzilla.suse.com/show_bug.cgi?id=1177461#c39
it seems that /run/rpcbind was already present with wrong permissions. So, I guess an "rm -rf /run/rpcbind" instead of a chown in the initrd would do.
Thanks Thomas. The /run/rpcbind directory is created by root in the initrd (see comment #6 - https://github.com/dracutdevs/dracut/blob/master/modules.d/95nfs/nfs-start-r...), that's why the chown is done after. Then, IIUC we can avoid the mkdir and the chown, because rpcbind will create /run/rpcbind if it does not exist, right? And, does the same apply to the /var/lib/rpcbind directory (see https://github.com/dracutdevs/dracut/blob/master/modules.d/95nfs/parse-nfsro...), could we skip that mkdir & chown? -- You are receiving this mail because: You are on the CC list for the bug.