Tavitayya Varanasi wrote: > > A symbolic link is created on apache as /var/apache2/2.2/htdocs/ganglia . > > End user can access it as http://localhost/ganglia .
I suppose that will work ok, but I'd avoid delivering any important package content into /var/apache2/2.2/htdocs. Since that is the content root of the users web site, it is most likely that customers will simply rm -rf everything in it when setting up their own content. This leaves the ganglia package corrupted. You could argue it is the customers fault, but given the circumstance it'd be hard to fault them. In short, I suggest instead delivering a /etc/apache2/2.2/conf.d/ganglia.conf file where you Alias the location of the webapp into /ganglia (or alternatively /etc/apache2/2.2/samples-conf.d/ganglia.conf if you want users to need to manually enable it). That will be cleaner and less surprising for customers and safer for the package. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
