Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://hea-www.harvard.edu/~fine/OSX/autofs-repl-fix.html
Дата изменения: Unknown Дата индексирования: Sun Apr 10 09:01:01 2016 Кодировка: Поисковые слова: п п п п п п п п п п п п |
☺ NOTE (December 2009): This bug has been fixed in Snow Leopard (10.6) ☺
foo -ro,hard,intr host1:/path1/& host2:path2/& host3:path3/foo_orig bar -ro,hard,intr host1,host2,host3:/path/& baz -ro,hard,intr host1,host2:/path1/& host3:path3/baz_orig
When the automounter sees an entry like this and tires to mount it, it's supposed to figure out which host is the "closest" and mount from that one. If that host is unavailable, it tries the next closest one. Furthermore, once filesystem is mounted, if the server has a problem and goes offline, the kernel has a mechanism by which it can fail over to another server, seamlessly.
[As of June '08 it's been reported to me (by an apparently reliable source) that OS X does not support this failover, which isn't surprising (I don't know of Linux versions that do either). But failing to failover isn't a showstopper, just a nuisance.]
Under Leopard 10.5.1 and 10.5.2 (so far), this does not work. Fortunately, Apple graciously makes portions of their code available, including autofs, so we were able to fix this problem. You'll need to become an Apple Developer Connection member to download autofs, but this is free. We downloaded the autofs-109 tarball (you can also browse the files) from under the 10.5.2 tree, and our patches are based on this version.
(Note that the information below has been passed on to Apple, so in theory a future release of OS X will not have these bugs!)
Apply these patches to the files in autofs-109/automountd/, and then rebuild.
I'm not much of an Xcode guru, but by hacking and thrashing about a bit
I got it to compile. What I did is stick mntopts.h into the
autofs-109/header directory. Then I edited the files that used
The Xcode build still fails, but it gets past automountd, which is
successfully built. You can then copy it out of the build directory
(build/Development/automountd, in our case since we had it set up
for a Development build) and into /usr/libexec/automountd. I suggest
you save a copy of the original automountd in case something goes
horribly wrong.
We haven't tested if there is any kind of failover [reportedly, no,
see
above], so for us that
remains to be seen. However getting the Leopard OS X to use our maps
in the general case has made it all worth while.
More Mac OS X Stuff
Using
It's worked great for us so far. If you have replicated server entries
in your NIS maps, it should work for you too.
Fine's Home
Send Me Email