1 Am-utils Frequently Asked Questions
3 Note: we started this FAQ only on March 15, 2005; so it's not long or
4 comprehensive, yet. Amd is much older than that, and so there's a lot of
5 information that's already available in other forms. If this FAQ doesn't
6 answer your questions, see information in the following sources:
8 1. The Am-utils book: http://www.am-utils.org/docs/amd-book/
10 2. The Am-utils user manual, which is part of the distribution and is also
11 available from www.am-utils.org.
13 3. The www.am-utils.org Web site resources, especially the "am-utils" mailing
14 list (and its archives).
16 4. In the am-utils distribution (always use the latest ones), see all of the
17 various README files (README, README.autofs, README.ldap, README.osx, and
18 README.y2k). The "BUGS" file also lists useful information about bugs
19 and problems with specific OSs which affect Amd. All of these text files
20 are also available from www.am-utils.org.
22 5. Some FAQ questions (including newbie questions) are available here:
23 http://www.kernelcorp.com/resources_faqs.html
25 6. Some problems are known bugs but have not been fixed yet: this are
26 listed in bugzilla in https://bugzilla.am-utils.org/
28 If you have additions to this FAQ, please let us know at
29 the am-utils list (see www.am-utils.org).
32 The Am-utils development team.
38 Q1. When I use Amd with Autofs and I restart Amd, how come it cannot remount
39 the Autofs partitions?
41 A1. This is a limitation of the Linux Autofs kernel module (for both autofs
42 v2. and v3). The Linux Autofs does not allow restarting automounted
43 points. There's nothing Amd can do about this. In fact, the same
44 problem exists if you use the userland "automount" daemon instead of
45 Amd. Hopefully Autofs-v4 or the separate effort of Autofs-NG will
46 address this serious problem.
48 Note that Amd itself can restart autofs automounted points just fine on
49 OSs that support it, for example Solaris.
52 Q2. When I use Amd, I get this console message frequently: "mount version
53 older than kernel." Is it a problem?
55 A2. No, it's a harmless warning message that the Linux kernel prints for NFS
56 mounts. The intent was to alert administrators that the kernel has
57 supposedly a different version of the mount(2) code than a userland
58 program used. This happens if you compile Amd against kernel headers
59 that are different than the kernel you're running. If the message
60 really bothers you, then one way to "fix" the problem is to recompile
61 Amd against the same kernel headers as the running kernel.
63 Nevertheless, it is a relatively useless message because as far as we
64 know, the NFS v2 and v3 mount codes have been in perfect sync between
65 the userland and kernel sides, and were "standardized" for years
66 already. This warning message caused more unnecessary worry among
67 administrators than helping alert them to legitimate problems.