Solved: Should /run/rpcbind be owned by xbian
|
14th Aug, 2013, 06:44 PM
Post: #1
|
|||
|
|||
Should /run/rpcbind be owned by xbian
I was having hard time to mount a nfs share to my xbian
Raspberry Pi, 512 MB (though reported 376 BM by system??) Xbian 1.0Beta1.1 Code: uname -a The mount command: Code: sudo mount -t nfs 192.168.1.106:/nfs /media/MyBookLive The error output was: Code: mount.nfs: rpc.statd is not running but is required for remote locking. I edited the /etc/default/nfs-common conf file, but the problem persissted. nsf-common refused to start anyway, because Code: [warn] Not starting: portmapper is not running ... (warning). After some fiddling, it turned out that Code: /run/rpcbind is owned by xbian, not by root. I changed ownership and the service started and i managed to mount. My question is this a bug, or this intended design and I am missing the point how to use the start the service here? |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Should /run/rpcbind be owned by xbian - deckoff - 14th Aug, 2013 06:44 PM
RE: Should /run/rpcbind be owned by xbian - mk01 - 14th Aug, 2013, 08:15 PM
RE: Should /run/rpcbind be owned by xbian - deckoff - 15th Aug, 2013, 03:08 PM
|