I'm running Tru64 v5.0A, but I am about to upgrade to v5.1 (tomorrow).
Currently /tmp is a symbolic link that points to
/cluster/members/{memb}/tmp
My system is not part of a cluster nor is it likely to be part of a
cluster any time in the near future. Apparently v5.0A sets up /tmp this
way by default. This was the result of a "normal" installation.
Right now the directory above is in my root_domain (I'm running AdvFS for
all file systems). There isn't a lot of space in my root_domain; currently
there is only about 160 MBytes free there. I'd like to point the /tmp
symbolic link to /var/tmp (which I notice is also a symbolic link to
/var/cluster/members/{memb}/tmp
I have lots of free space on my var_domain and this seems like an
appropriate place to put the system /tmp directory. Are there any (bad)
implications of doing this that I should know about? Will mixing files
from /tmp with /var/tmp cause any applications to do odd things?
How important is it to me that /tmp be located in a cluster member
specific directory? Another approach would be for me to create a new
fileset in the var_domain and then mount that file set right on a /tmp
directory. This would keep /tmp and /var/tmp distinct but it would
disassociate /tmp from the cluster member information. Is that important?
Thanks for any advice you can offer.
Peter
Received on Mon Apr 30 2001 - 14:20:53 NZST