Re: [cobalt-users] httpd running but no web except Cobalt GUI

["Steve Werby" <steve-lists@xxxxxxxxxxxx>]

"MikeM" <mike_miller@xxxxxxxxxxxxxxxxxx> wrote:
> >   BTW, the Cobalt GUI runs on a different port
> > (port 81) than the regular webserver.  You may have known that,
> > just thought
> > I'd mention to clarify why that's accessible.
>
>
> I suspect the Cobalt GUI runs on more than just a different port.  If you
do
> a netstat -pl, you'll notice that the Cobalt GUI instance of Apache has a
> different PID than the Apache that serves up the web pages. [at least,
that
> is the way it is on my RaQ3]

This is correct (perhaps I should have mentioned it), but multiple instances
of Apache on port 80 can be running concurrently and each will have a
different PID as well.  Every time a process is run it gets a new PID.  It's
pretty common for a webserver to have httpd running many times concurrently.

> I suspect there may be two separate instances of Apache running, one for
the
> Cobalt GUI and the other for the web pages.  This will give some measure
of
> failsafe-ness [is that a word?] to the administration screens when the web
> page Apache is modified and has its config files altered.

There is definitely a separate Apache binary for the admin interface which
runs on port 81.  The binary is at /usr/sbin/ahttpd, while the regular
webserver is at /usr/sbin/httpd.  When each of these processes is first
started their PIDs are recorded in /var/run (along with those of a number of
other processes).  See /var/run/admserv.pid and /var/run/httpd.pid if you
ever need to reference their PIDs.

--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/