Martijn,
Maybe I'm missing something, but in this case wouldn't using .htaccess
be a good approach?
spike
Martijn wrote:
Hello everyone,
I've been trying to solve this for the last 2 days, but somehow I'm
unable to see the logic here. Hope anyone can help me explain what's
going on:
Isabelle,
In your VirtualHost directive try:
VirtualHost http://www2n.unil.ch:8080 http://www2n.unil.ch
spike
Isabelle Moullet wrote:
Bonjour,
I am trying to install mass virtual hosting with Apache 2.0.53.
I have the the following instructions in my conf file:
#
LoadModule
Jody,
Check to make sure that the username which apache is running under has
read access for the /home, /home/cleveland /home/cleveland/password
directories. If you're apache is running as 'nobody' then you'll
probably need 744 on the directory files themselves. The other
possibility is
- this screen
/usr/local/apache/bin/apachectl stop: httpd stopped
Joshua Slive wrote:
On 8/15/05, Spike Burkhardt [EMAIL PROTECTED] wrote:
All,
I have two apache instances running. Is there a way to kill just 1
instance? To be more specific, I have 1 startup file with the standard
Thanks for all the info Joshua. Seems like I might have a reason to
upgrade to V2 :-)
spike
Joshua Slive wrote:
On 8/16/05, Spike Burkhardt [EMAIL PROTECTED] wrote:
Joshua all,
When I specified the configuration file the instance I wanted to kill
still didn't stop. In fact
Jody,
Just a suggestion on my part but perhaps doing a apachectl configtest
would yield more information.
spike
Jody Cleveland wrote:
Are you trying to start it as root (required for ports like 80 443)?
Yes, I am.
I would search for 443 in your {server}/conf/httpd.conf file.
Oliver,
A total guess is that there are too many files open! lol. Sorry,
had to do it. On Solaris, the number of files open at any one time is
based on system and process limits. Even though it's old a good
reference article is
