diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20120310/006670.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20120310/006670.html | 112 |
1 files changed, 112 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120310/006670.html b/zarb-ml/mageia-discuss/20120310/006670.html new file mode 100644 index 000000000..60b5f0025 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120310/006670.html @@ -0,0 +1,112 @@ +<!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=%3C4F5AB071.5030307%40Rock3d.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006669.html"> + <LINK REL="Next" HREF="006671.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=%3C4F5AB071.5030307%40Rock3d.net%3E" + TITLE="[Mageia-discuss] home network using broadband router">imnotpc at Rock3d.net + </A><BR> + <I>Sat Mar 10 02:37:53 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="006669.html">[Mageia-discuss] home network using broadband router +</A></li> + <LI>Next message: <A HREF="006671.html">[Mageia-discuss] home network using broadband router +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6670">[ date ]</a> + <a href="thread.html#6670">[ thread ]</a> + <a href="subject.html#6670">[ subject ]</a> + <a href="author.html#6670">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 03/09/2012 07:34 PM, WALKER RICHARD wrote: +><i> This works for the nfs server on 2010.2 and Mageia 1 (with the bodge +</I>><i> in /etc/sysconfig/nfs-server) +</I>><i> +</I>><i> /etc/exports; +</I>><i> # generated by drakhosts.pl +</I>><i> /home/richmag/Videos +</I>><i> 192.168.0.0/8(no_all_squash,async,secure,no_subtree_check,rw) +</I>><i> +</I>><i> The client machine is always 2010.0 and the /etc/fstab entry for the +</I>><i> Mageia 1 server is +</I>><i> 192.168.0.101:/home/.rich64/Videos /mnt/Videos nfs +</I>><i> user,rsize=8192,wsize=8192,noauto,soft 0 0 +</I> +I've done a little testing on my own. My nfs server is on a Fedora box +and I set my client fstab entries by hand, so I hadn't used the Mageia +tools until today. It seems MCC doesn't create an nfs4 share by default +(it uses the older protocol) so this is a little different from what +I've been doing and I'm a bit rusty. A couple points... + +You didn't answer my question about whether or not Smoothwall always +assigns the same IP to the server box. This is important since if it +doesn't then every time the server restarts the network interface you +are taking a chance it will get assigned a different IP and break the +client fstab entries. + +Has this configuration ever worked correctly? The exports file looks +fine but IIRC the fstab entry should match the exports file path, i.e. +it should be: "192.168.0.101:/home/richmag/Videos /mnt/Videos ...." + +><i> Starting the nfs server from the MCC Services list on the Mageia 1 +</I>><i> system produces this pop-up response with a normal setup; +</I>><i> Stopping NFS kernel daemon +</I>><i> Stopping rpc.mountd:[FAILED] +</I>><i> stopping nfsd:[FAILED] +</I>><i> Unexporting directories for NFS kernel daemon... +</I>><i> Exporting directories for NFS kernel daemon... +</I>><i> Starting NFS kernel daemon +</I>><i> Starting nfsd[ OK ] +</I>><i> Starting rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> rpc.mountdrpc.mountd:svc_tli_create:could not bind to requested address +</I>><i> [ OK ] +</I> +This looks like you have a version of the nfs server already running +that is using the assigned port which also might explain why disabling +the port configuration worked, at least once anyway until the default +port had a server running on it as well. I think you need check and see +if there is an existing daemon running and if so why it isn't shutting down. + +Jeff +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006669.html">[Mageia-discuss] home network using broadband router +</A></li> + <LI>Next message: <A HREF="006671.html">[Mageia-discuss] home network using broadband router +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6670">[ date ]</a> + <a href="thread.html#6670">[ thread ]</a> + <a href="subject.html#6670">[ subject ]</a> + <a href="author.html#6670">[ 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> |