Joined: 06 Aug 2013 Posts: 2 Location: Somewhere in Washington
Posted: Thu Aug 29, 2013 18:03 Post subject:
Sorry to dig up an ancient thread, but hopefully this might help someone else.
I am running kong mega 220000 on a linksys e4200. I have optware2 installed and am running
I noticed I was getting this same xinetd spam about starting www in wallwatcher.
I also noticed even though pixelserv moves httpd to port 88, I was still listening on port 80.
using netstat -l -v --numeric-ports -p I discovered xinetd was the culprit. I don't know if this is by design, or what, I am still researching.
Anyway, if I connected to the admin page using port 88 I don't get the xinetd messages.
However if I connect to the admin page using port 80, not only do I still get the admin page, xinetd is going nuts. (It appears it's spawning a www process that immediately dies, so in order to fulfill all the http requests it keeps starting them)
Anyhow, I am still investigating why xinetd is doing this(for all I know it's by design) I may look at just blocking port 80.
Allows a tcp service to be redirected to another host. When xinetd receives a tcp connection on this port it spawns a process that establishes a connection to the host and port number specified, and forwards all data between the two hosts. This option is useful when your internal machines are not visible to the outside world. Syntax is: redirect = (ip address) (port). You can also use a hostname instead of the IP address in this field. The hostname lookup is performed only once, when xinetd is started, and the first IP address returned is the one that is used until xinetd is restarted. The "server" attribute is not required when this option is specified. If the "server" attribute is specified, this attribute takes priority.