What version of the client are you using?
We've found that using the VIRTUALMOUNTPOINT option works for us,
using SGI client (PTF 5 and 6). The VIRTUALMOUNTPOINT is made on
the mountpoint directory (in your case /home/xxx). We then create
a domain statement in the options file for each of the
VIRTUALMOUNTPOINT entries.
When you use this method, you end up with each home directory as
a separate filespace, which turns out to be a benefit for us as
we can easily export/import home directories from one client to
another, as machines tend to get swapped a lot in our
environment.
-- Tom
On Thu, 25 Mar 1999, Klaus Steinberger wrote:
>Hello,
>
>I'm currently in the process of moving from amd to autofs Automounter
>on HP/SGI/Linux systems.
>
>My hope is to get rid of the weird automounter mountpoints
>(/a/machinename/....), and instead get inplace mounts.
>
>This works well on all three system types. But I do have an problem
>with dsm or dsmc.
>
>I have for example a filesystem with the real mountpoint /export/home/xxx
>autofs mounts this inplace as /home/xxx.
>
>dsm works well if this is mounted via nfs. I then see this filesystem
>in the network filespaces for archive or backup if its mounted remotely.
>
>But local I do see it in local filespace as export/home/xxx
>even if automount has mounted it inplace with the lofs filesystem.
>
>I do have an common ADSM Node for all of our user filespaces, so I want
>to see it also as /home/xxx on the local machine, so that if the users
>do archiving or restoring they always see /home/xxx as the filespace
>regardless on which machine they started dsm.
>
>How could I do that. I tried already virtualmountpoint, but that didn't help.
>
>Sincerely,
>Klaus
>--
>Klaus Steinberger Beschleunigerlabor der TU und LMU Muenchen
>Phone: (+49 89)289 14287 Hochschulgelaende, D-85748 Garching, Germany
>FAX: (+49 89)289 14280 EMail: Klaus.Steinberger AT
>Physik.Uni-Muenchen DOT DE
>URL: http://www.bl.physik.tu-muenchen.de/~k2/
>In a world without fences and walls, who needs Windows and Gates?
>
|
