On 16/06/12 08:20, AL13N wrote: > Op zaterdag 16 juni 2012 09:43:42 schreef Sander Lepik: [...] >> After installation, all the 192.168.0.40 mounts work, the >> 192.168.0.200 ones don't. More digging to be done. >> >>>> The errors for those two are: >>>> >>>> 'mount.nfs: rpc.statd is not running but is required for >>>> remote locking. mount.nfs: Either use '-o nolock' to keep >>>> locks local, or start statd. mount.nfs: an incorrect mount >>>> option was specified' >>>> >>>> Not sure what I have to do about statd - my efforts don't >>>> seem to have >> >> achieved much. > [...] > > doesn't this mean that 192.168.0.200 hasn't had statd started? > check with rpcinfo -p 192.168.0.200. > statd is not listed among the services by that command. However, Frank's suggestion has fixed things. I'm a little out of my depth, but if there are any lessons to be learned by checking configs I'm happy to do so.
Anne -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org
