blob: f038c14b8e97a20ab2fc9ec1004ae4eb488784a0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] fstab problem
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20fstab%20problem&In-Reply-To=%3C4FDB9A5E.1060502%40roadrunner.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="007894.html">
<LINK REL="Next" HREF="007896.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] fstab problem</H1>
<B>Frank Griffin</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20fstab%20problem&In-Reply-To=%3C4FDB9A5E.1060502%40roadrunner.com%3E"
TITLE="[Mageia-discuss] fstab problem">ftg at roadrunner.com
</A><BR>
<I>Fri Jun 15 22:26:06 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="007894.html">[Mageia-discuss] fstab problem
</A></li>
<LI>Next message: <A HREF="007896.html">[Mageia-discuss] fstab problem
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7895">[ date ]</a>
<a href="thread.html#7895">[ thread ]</a>
<a href="subject.html#7895">[ subject ]</a>
<a href="author.html#7895">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 06/15/2012 02:54 PM, Anne Wilson wrote:
><i> On 15/06/12 19:13, Frank Griffin wrote:
</I>>><i>
</I>>><i> Shortly before release I and others noticed that a lot of basic services
</I>>><i> that were converted to systemd were no longer starting automatically at
</I>>><i> boot. I thought that it was fixed, but you might check to see that NFS
</I>>><i> has actually been started.
</I>><i>
</I>><i> Combining replies:
</I>><i>
</I>><i> Sander: nfs-utils-clients wasn't installed on the misbehaving laptop.
</I>><i> After installation, all the 192.168.0.40 mounts work, the
</I>><i> 192.168.0.200 ones don't. More digging to be done.
</I>><i>
</I>><i> The errors for those two are:
</I>><i>
</I>><i> 'mount.nfs: rpc.statd is not running but is required for remote locking.
</I>><i> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
</I>><i> mount.nfs: an incorrect mount option was specified'
</I>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".
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007894.html">[Mageia-discuss] fstab problem
</A></li>
<LI>Next message: <A HREF="007896.html">[Mageia-discuss] fstab problem
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7895">[ date ]</a>
<a href="thread.html#7895">[ thread ]</a>
<a href="subject.html#7895">[ subject ]</a>
<a href="author.html#7895">[ 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>
|
