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-dev/2012-March/013434.html | 109 ++++++++++++++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-March/013434.html (limited to 'zarb-ml/mageia-dev/2012-March/013434.html') diff --git a/zarb-ml/mageia-dev/2012-March/013434.html b/zarb-ml/mageia-dev/2012-March/013434.html new file mode 100644 index 000000000..ad242e885 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013434.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] rescue has mount.nfs, but no statd + + + + + + + + + +

[Mageia-dev] rescue has mount.nfs, but no statd

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Mar 23 10:34:55 CET 2012 +

+
+ +
On 22 March 2012 20:33, Maarten Vanraes <alien at rmail.be> wrote:
+>> nfs was available, so we wanted to mount
+>>
+>> but the mount failed, because nfs module wasn't modprobed, and drvinst
+>> didn't fix that (maybe it should modprobe nfs as well)
+>>
+>> or maybe mount.nfs should try to modprobe nfs if needed.
+>>
+>> however, statd wasn't there and it complained that it needed that for
+>> locking
+>>
+>> atm we're doing -o nolock and that works... but... statd would be quite
+>> usefull here...
+>
+> perhaps i should rephrase...
+>
+> can i fix this by adding statd on the rescue? or would this take too much
+> space?
+
+it's simpler to use "mount -o nolock" instead...
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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