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