[users] /opt/csw

Gary Armstrong warden at mail.testedgeinc.com
Wed Mar 24 16:46:38 CET 2004



Oscar del Rio wrote:

> Gary Armstrong wrote:
>
>> Since they all default to loading in /opt/csw, what's the recommended 
>> way to load something local? Currently, I'm automounting /opt/csw 
>> using a direct map.
>>
>> For instance, if I want to run apache on 2 machines, what's the 
>> blastwave recommendation, for where/how the installs should be done.
>
>
> Speaking only for myself, not for blastwave:  :-)
>
> You can install apache on the NFS server just like any other CSW
> package, and on the NFS clients that will run the apache daemon
> keep the conf file in a local dir, e.g. /etc/apache
> Make a /etc/init.d/ startup script to run
> /opt/csw/apache/bin/httpd -f /etc/apache/conf/httpd.conf
>
> In the local config file make sure the paths for DocumentRoot
> and log files are in a local dir.

I am leaning this way. Anyway, blastwave might consider a second 
directory (ie csw-l), for things that should be configured locally. It 
also makes them easy to spot. That way if some software package is 
configured for the host I installed on, it doesn't get automounted on 
another.

Thanks
Gary


>
> Alternatively, you can
> cd /opt/csw/apache
> mv conf conf.csw; ln -s /etc/apache/conf
> mv logs logs.csw; ln -s /etc/apache/logs
> mv htdocs htdocs.csw; ln -s /etc/apache/htdocs
>
> but be careful when you upgrade the apache package.
>
> _______________________________________________
> users mailing list
> users at lists.blastwave.org
> https://lists.blastwave.org/mailman/listinfo/users
>
>





More information about the users mailing list