Bill Jonas on Fri, 28 Apr 2000 11:02:27 -0400 (EDT) |
On Fri, 28 Apr 2000, Luis Baars wrote: >only if you have httpd is tcp wrapped (this is where my lack of knowledge >comes in because I don't know if httpd can be tcp wrapped, I'm assuming it >can because it deals with packets coming into the computer). It *can* be, but one wouldn't want to do it that way. The reason being is that for *each incoming request*, httpd would start, serve the request, and then die. Keep in mind that the page itself is one request, as well as each graphic on the page. If you, say, only want people within your organization to be able to view your pages (*.domain.tld, for example) and it won't be serving up more than a couple pages a minute, it might not be a bad idea. Otherwise, you really want it to run as a stand-alone service. (You might even be able to specify domains in some httpd configuration file like with tcp wrappers, but I don't know, as I've not set up a web server either, although I may get some practice with that soon.) It might not be a bad idea to check the inetd.conf, though, to make sure it's not being run as a wrapped service (although I doubt that RH would setup their default configuration that way). And don't forget to 'killall -HUP tcpd' if you make changes to inetd.conf. Have a lot of fun, :) Bill -- (Clever, funny, and/or witty comment goes here.) Harry Browne for President: http://www.harrybrowne2000.org/ Visit me at http://www.netaxs.com/~bj/ ______________________________________________________________________ Philadelphia Linux Users Group - http://plug.nothinbut.net Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
|
|