[lug] Concurrent apache's
Atkinson, Chip
CAtkinson at Circadence.com
Fri Sep 15 13:39:50 MDT 2000
That's weird. Can you tail -f the log files? Perhaps it'll be in
/var/log/messages as to why it's dying.
-----Original Message-----
From: Ken Kinder [mailto:ken at kenkinder.com]
Sent: Friday, September 15, 2000 1:38 PM
To: 'lug at lug.boulder.co.us'
Subject: RE: [lug] Concurrent apache's
That's exactly what I'm doing. It just mysteriously dies. The test port is
supposed to 8880
--
Ken Kinder
www.kenkinder.com
On Fri, 15 Sep 2000, Atkinson, Chip wrote:
> You can start apache with the -d for the serverroot, the -f to specify the
> configuration file, and in the different configuration files, you can
> specify which port to listen to with the Listen directive to tell what
port
> to listen on. We did this to use the same machine for testing as well as
> production on the corp. intra net. The test httpd listened on port 81 and
> the regular production listened on port 80.
>
> Chip
>
> -----Original Message-----
> From: Ken Kinder [mailto:ken at kenkinder.com]
> Sent: Friday, September 15, 2000 1:21 PM
> To: lug at lug.boulder.co.us
> Subject: [lug] Concurrent apache's
>
>
> Apache seems to die if you try to have several instances of it running on
> different ports, different config files, etc. Does anyone know how to work
> around that?
>
> --
> Ken Kinder
> www.kenkinder.com
>
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>
_______________________________________________
Web Page: http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
More information about the LUG
mailing list