Thanks to:
Jochen Bern <bern@TI.Uni-Trier.DE>
Richard Dodds <Richard.Dodds@sv.sc.philips.com>
Rich Kulawiec <rsk@gsp.org>
Rich Pieri <rich.pieri@prescienttech.com>
"Mike Salehi" <mrs@cadem.mc.xerox.com>
The consensus is, no, solaris can't do it,
but there are 2 kluges people came up with...
1. Creating a new "install" directory for each
user, where all files and directories of the
real install dir are symlinks - except the library
that is to be unique by user...then, all libraries
that are shared need to be symlinks also.
The disadvantage is that this requires 131 links
per user, rather than the handful it would require
if the symlink idea was supported.
2. automounter - where a mount point can be
determined from a userid. I have not tried this,
but it makes sense.
Thanks for all your help.
Seth
- - - - - - - - - - - - - - - - - -
I think, you should be able to do it with automount, but
I think he will need to have all the environmental variables declared
at the time of starting.
Mike (Mehran) Salehi mrs@cadem.mc.xerox.com (716)422-2725
- - - - - - - - - - - - - - - - - -
I've seen it on Apollo's, where they'ld consequently call that a
SOFTlink
rather than a SYMlink, but not on SUNs, I'm afraid. The Apollo's used
this to let the User choose his favorite Unix Flavor (of which these
Boxes offered several at once) - i.e., /usr being a Softlink to, say,
/os/$FLAVOR/usr with the default Flavor sitting in /os/usr ...
However, that was several Years ago ...
Regards,
J. Bern
- - - - - - - - - - - - - - - - - -
Can you accomplish this by putting a shell wrapper around the
invocation of the database product that (1) adjusts the symlinks
to what they need to be and then (2) invokes the database?
---Rsk
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:30 CDT