In theory, there's no need for your fileservers to use the automounter.Even if you make the filesystems visible under their normal names aswell as in /export , you could mount them explicitly in /etc/vfstab .However, doing so would significantly complicate our environment,because it turns out that the automounter worries about a number ofissues for us.

Of course, one big reason to use the automounter is administrativeconvenience; you can use the same set of automounter maps on yourfileservers as you do

One of my peculiar traits is that I test error paths, sometimesobsessively. If I write an error check into my code, I am not happyuntil I have induced the error and watched the error check firecorrectly. Judging from some of the code that I've seen this makes me ararity, but it shouldn't be this way.

In fact, I sometimes think that explicitly testing error paths is moreimportant than explicitly testing regular code paths. It is usuallypretty obvious when regular code paths don

On Solaris, there is a combination gotcha with the automounter and mountson the same host. It goes like this:

1. your fileserver normally has /dev/whatever mounted on /export/foo.
2. your generic automounter configuration mounts fileserver:/export/fooas /foo.
3. you need to do some maintenance to the filesystem, so you unshareand unmount /export/foo.
4. after you're done you try to remount it, but you get a message thatthe mount point is busy. The only mention of