Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Teamsite install on symbolic links
kannan_r
hi
wehad to install TS last week on a server which had
df -kh
Filesystem Size Used Avail Use% Mounted on
LogVol00 4.9G 409M 4.2G 9% /
LogVol06 3.0G 285M 2.5G 11% /tmp
LogVol03 3.9G 1.9G 1.9G 50% /usr
LogVol01 2.0G 68M 1.8G 4% /home
LogVol05 2.0G 278M 1.6G 15% /usr/local
/dev/cciss/c0d0p1 99M 12M 83M 13% /boot
tmpfs 1014M 0 1014M 0% /dev/shm
VolGroup 79G 6.7G 73G 9% /opt/Interwoven
Only /opt/interwoven had the max space so few choices installing TS on /opt/interwoven volume.
just to maintian consistency with dev /QA servers we had to create symlinks to
1) /Interwoven -> /opt/Interwoven/
2)/iwmnt -> /opt/Interwoven/iwmnt/
3) /iw-store to /opt/Interwoven/iw-store
after that installed TS to their default paths ie /Interwoven/Teamsite and /iwmnt /iw-store
question now is have we done any thing that is not supported or recommended ?
I am asking this question due to two reasons
Since I am the only user right now , can format /reinstall OS with sufficient space to root partition and install TS all over again.
two : issue is much simpler as there are no users or any live content now, future when users start using TS and there is live content ,do want any issues due to the way TS is installed.
Let me know your thoughts ?
Find more posts tagged with
Comments
Adam Stoller
If you have the option to wipe/re-format/re-install as desired - I'd take it.
Symbolic links can be nice, but they can also cause problems, often in strange and difficult to discern ways. So, if you're choice is between losing a couple of hours to re-configure the hardware vs. potentially losing hours, days, even weeks of time later trying to debug a problem caused by the use of a symlink.... well you get the picture.
nipper
I would NOT use symlinks, nor NFS mounts for your TS install. TS likes to have SetUID files and NFS does not allow setuid files (by default) and your admin will need to allow it.
Also, performance wise, all TS IO operations will need to run over NFS which is much slower than your local disk.
So if performance is not an issue, reinstall it on an NFS mount that allows local root access and setuid.
If performance is an issue, put it on a local disk.
And DO NOT MESS WITH /iwmnt it is a virtual mount point and there is no reason to change it.