From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-discuss/20120615/007895.html | 80 +++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 zarb-ml/mageia-discuss/20120615/007895.html (limited to 'zarb-ml/mageia-discuss/20120615/007895.html') diff --git a/zarb-ml/mageia-discuss/20120615/007895.html b/zarb-ml/mageia-discuss/20120615/007895.html new file mode 100644 index 000000000..f038c14b8 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120615/007895.html @@ -0,0 +1,80 @@ + + + + [Mageia-discuss] fstab problem + + + + + + + + + +

[Mageia-discuss] fstab problem

+ Frank Griffin + ftg at roadrunner.com +
+ Fri Jun 15 22:26:06 CEST 2012 +

+
+ +
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".
+
+ + + + +
+

+ +
+More information about the Mageia-discuss +mailing list
+ -- cgit v1.2.1