apache under inetd/tcpd: it's dead, isn't it?
Not looking for a list of reasons why this isn't a good idea, just simply: is anybody out there successfully running apache httpd 1.3.12 or later under SuSE linux 6.4 or later inetd/tcdp? Being a troglodyte, I had to try it; I couldn't get it to work (nobody home on port 80), and didn't spot anything in various logs. The things I set were: /etc/rc.config: START_HTTPD=no httpd.config: ServerType inetd /etc/inetd.conf: httpd stream tcp nowait root <path to tcpd> (continued line) <path to apache> -f <path to httpd.conf> (continued line) <standard modules> (I also tried wwwrun instead of user root, and without tcpd.) Oh well, on to more productive things. -- Fred Morris m3047@inwa.net
Just out of curiosity, I wonder what would happen if instead of using "apache -f conf file" you just used the path to the regular SusE initscript for apache "/usr/sbin/rcapache start". I'm almost 100% sure that inetd won't be able to kill it, but it'd be interesting to see if it at least can start it that way (after all, on SusE that is the correct way to start apache) At 12:44 PM 1/26/2002 -0800, you wrote:
Not looking for a list of reasons why this isn't a good idea, just simply: is anybody out there successfully running apache httpd 1.3.12 or later under SuSE linux 6.4 or later inetd/tcdp?
Being a troglodyte, I had to try it; I couldn't get it to work (nobody home on port 80), and didn't spot anything in various logs. The things I set were:
/etc/rc.config: START_HTTPD=no
httpd.config: ServerType inetd
/etc/inetd.conf: httpd stream tcp nowait root <path to tcpd> (continued line) <path to apache> -f <path to httpd.conf> (continued line) <standard modules>
(I also tried wwwrun instead of user root, and without tcpd.)
Oh well, on to more productive things.
--
Fred Morris m3047@inwa.net
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
On Sat, 26 Jan 2002 12:44:14 -0800, m3047@inwa.net (Fred Morris) wrote:
Not looking for a list of reasons why this isn't a good idea, just simply: is anybody out there successfully running apache httpd 1.3.12 or later under SuSE linux 6.4 or later inetd/tcdp?
Being a troglodyte, I had to try it; I couldn't get it to work (nobody home on port 80), and didn't spot anything in various logs. The things I set were:
/etc/rc.config: START_HTTPD=no
httpd.config: ServerType inetd
/etc/inetd.conf: httpd stream tcp nowait root <path to tcpd> (continued line) <path to apache> -f <path to httpd.conf> (continued line) <standard modules>
(I also tried wwwrun instead of user root, and without tcpd.)
If you use 'httpd' in /etc/inetd.conf, check that you have a matching port definition in /etc/services. Also (checking for the "d'oh" factor) inetd has had a chance to re-read the config file, hasn't it? Richard. ----- Richard P. Scott, Lincoln, England. richard@fortress.demon.co.uk
At 11:34 PM 1/26/2002 +0000, you wrote:
On Sat, 26 Jan 2002 12:44:14 -0800, m3047@inwa.net (Fred Morris) wrote: If you use 'httpd' in /etc/inetd.conf, check that you have a matching port definition in /etc/services.
Good point, but actually he needs to hange "htppd" to "http" for standard /etc/services. That might be why his way isn't working.
Also (checking for the "d'oh" factor) inetd has had a chance to re-read the config file, hasn't it?
Yeah don't forget "rcinetd restart"
Richard. ----- Richard P. Scott, Lincoln, England. richard@fortress.demon.co.uk
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
participants (3)
-
JW -
m3047＠inwa.net -
Richard P.Scott