summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20120312/006700.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/20120312/006700.html')
-rw-r--r--zarb-ml/mageia-discuss/20120312/006700.html104
1 files changed, 104 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120312/006700.html b/zarb-ml/mageia-discuss/20120312/006700.html
new file mode 100644
index 000000000..1db7a4288
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20120312/006700.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] home network using broadband router
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20home%20network%20using%20broadband%20router&In-Reply-To=%3C4F5D34F2.1040503%40Rock3d.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+
+ <LINK REL="Next" HREF="006701.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] home network using broadband router</H1>
+ <B>imnotpc</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20home%20network%20using%20broadband%20router&In-Reply-To=%3C4F5D34F2.1040503%40Rock3d.net%3E"
+ TITLE="[Mageia-discuss] home network using broadband router">imnotpc at Rock3d.net
+ </A><BR>
+ <I>Mon Mar 12 00:27:46 CET 2012</I>
+ <P><UL>
+
+ <LI>Next message: <A HREF="006701.html">[Mageia-discuss] How to prune urpmi-proxy cache?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6700">[ date ]</a>
+ <a href="thread.html#6700">[ thread ]</a>
+ <a href="subject.html#6700">[ subject ]</a>
+ <a href="author.html#6700">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 03/11/2012 05:59 PM, WALKER RICHARD wrote:
+&gt;<i> On 10/03/2012, imnotpc&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">imnotpc at rock3d.net</A>&gt; wrote:
+</I>&gt;&gt;<i> You mentioned in an earlier post that the mga1 box worked once after you
+</I>&gt;&gt;<i> commented out the RPCMOUNTD_OPTIONS=&quot;--port 4003&quot; option in
+</I>&gt;&gt;<i> /etc/sysconfig/nfs-server. I just checked the mga1 test server I set up
+</I>&gt;&gt;<i> yesterday and this option isn't set at all. Is it possible you are
+</I>&gt;&gt;<i> mixing files from different Mandriva/Mageia versions? Perhaps try
+</I>&gt;&gt;<i> un-installing nfs-utils and deleting all it's config files and start
+</I>&gt;&gt;<i> again with a clean package install.
+</I>&gt;&gt;<i>
+</I>&gt;<i> Hi Jeff, it took a little more time than I thought but I have found
+</I>&gt;<i> the cause and the cure for the problem with nfs-server function on
+</I>&gt;<i> Mageia 1. In the process I learned how to use an rpm source package to
+</I>&gt;<i> patch and rebuild the offending file for the nfs-utils package.
+</I>&gt;<i> Tomorrow; the World!
+</I>&gt;<i>
+</I>&gt;<i> First up, the problem is well known and of quite some vintage. It only
+</I>&gt;<i> affected nfs-utils v1.2.3 so versions just prior and subsequent (as in
+</I>&gt;<i> v1.2.5 in Mageia 2 Cauldron) are OK. Hence the Mandriva 2010.2 worked
+</I>&gt;<i> as did my MGA2 Beta1 server.
+</I>&gt;<i>
+</I>&gt;<i> This reference tells the whole story;
+</I>&gt;<i> <A HREF="https://bugzilla.linux-nfs.org/show_bug.cgi?id=190">https://bugzilla.linux-nfs.org/show_bug.cgi?id=190</A>
+</I>&gt;<i>
+</I>&gt;<i> So the proposed fix was first seen in October 2010. I have used the
+</I>&gt;<i> proposed patch to rebuild the nfs-utils-1.2.3-2.1.mga1 package and it
+</I>&gt;<i> works perfectly well with the --ports option for rpc.mountd.
+</I>
+Very good.
+
+&gt;<i> In the course of all this I can confirm your observation that in a
+</I>&gt;<i> fresh MGA1 install of the nfs server the RPCMOUNTD_OPTIONS= entry is
+</I>&gt;<i> blank in /etc/sysconfig/nfs-server. My guess is that it is only set to
+</I>&gt;<i> a specific port number when you use the personal firewall with a hole
+</I>&gt;<i> for NFS. I don't see how you could configure the firewall if the
+</I>&gt;<i> listening port were to be some random value, so I reckon it's a good
+</I>&gt;<i> guess.
+</I>&gt;<i>
+</I>&gt;<i> I'll report this bug for the MGA1 package and we should have the fixed
+</I>&gt;<i> version out quite soon.
+</I>
+This is an age old issue with these tools since they were originally
+designed to use random ports prior to the common use of client
+firewalls. I've been hacking their config files since I first started
+using Linux to force them to use specific ports and it's always been a
+PITA. As annoying as these issues are they are at least not as bad as
+trying to get Samba to work in a heterogeneous network. Glad you got it
+figured out.
+
+Jeff
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+
+ <LI>Next message: <A HREF="006701.html">[Mageia-discuss] How to prune urpmi-proxy cache?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6700">[ date ]</a>
+ <a href="thread.html#6700">[ thread ]</a>
+ <a href="subject.html#6700">[ subject ]</a>
+ <a href="author.html#6700">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>