On 01/01/18 11:27, Ed Greshko wrote:
I think I'll take some time later today to setup a NFS server and
mount a partition
from another system to see if it causes an issue with the update.
FWIW, I have enabled the nfs.service on the VM and exported and mounted a partition
on a remote system and then did the same update as earlier.
Complete!
real 2m24.065s
user 0m19.020s
sys 0m37.675s
[root@f27k ~]# exportfs
/syntegra 192.168.1.0/24
[root@f27k ~]# ps -eaf | grep rpc
root 624 2 0 12:39 ? 00:00:00 [rpciod]
root 1800 1 0 12:43 ? 00:00:00 /usr/sbin/rpc.idmapd
rpc 1802 1 0 12:43 ? 00:00:00 /usr/bin/rpcbind -w -f
rpcuser 1806 1 0 12:43 ? 00:00:00 /usr/sbin/rpc.statd
root 1814 1 0 12:43 ? 00:00:00 /usr/sbin/rpc.mountd
root 1942 1735 0 12:53 pts/1 00:00:00 grep --color=auto rpc
[root@f27k ~]# ps -eaf | grep rpc
root 624 2 0 12:39 ? 00:00:00 [rpciod]
root 2259 1 0 12:56 ? 00:00:00 /usr/sbin/rpc.idmapd
root 2260 1 0 12:56 ? 00:00:00 /usr/sbin/rpc.mountd
rpc 2326 1 0 12:56 ? 00:00:00 /usr/bin/rpcbind -w -f
root 29412 1735 0 12:57 pts/1 00:00:00 grep --color=auto rpc
So, I am unable to duplicate the problem in any configuration that I can think of.
So, maybe the knee-jerk reaction to blame systemd is unwarranted?
If anyone can think of a configuration or other item that should be running to
duplicate the problem let me know. I've got the VM snapshot so....
--
Fedora Users List - The place to go to speculate endlessly