[Mageia-discuss] fstab problem
Anne Wilson
annew at kde.org
Sun Jun 17 11:46:38 CEST 2012
On 15/06/12 21:26, Frank Griffin wrote:
> On 06/15/2012 02:54 PM, Anne Wilson wrote:
>> On 15/06/12 19:13, Frank Griffin wrote:
>>>
>>> Shortly before release I and others noticed that a lot of
>>> basic services that were converted to systemd were no longer
>>> starting automatically at boot. I thought that it was fixed,
>>> but you might check to see that NFS has actually been started.
>>
>> Combining replies:
>>
>> Sander: nfs-utils-clients wasn't installed on the misbehaving
>> laptop. 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'
> rpc.statd was one of the things that wasn't getting started
> automatically.
>
> Try "service rpcbind start". If the mount works then, do a
> "systemctl enable rpcbind.service".
Bingo! Is that a permanent fix, or do I have to put it into a startup
file?
Anne
--
Need KDE help? Try
http://userbase.kde.org or
http://forum.kde.org
More information about the Mageia-discuss
mailing list