The following reply was made to PR os-linux/1893; it has been noted by GNATS.
From: Dean Gaudet <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: os-linux/1893: Server halts for apparently no reason Date: Sun, 1 Mar 1998 17:10:41 -0800 (PST) ---------- Forwarded message ---------- Date: Sun, 1 Mar 1998 17:32:25 -0700 (MST) From: ROOT <[EMAIL PROTECTED]> To: Dean Gaudet <[EMAIL PROTECTED]> Subject: Re: os-linux/1893: Server halts for apparently no reason Do you find this only on redhat 5.0's? I believe this same problem happened (not as cmomonly) when I had 4.2, 4.1 and 4.0 (which use libc-5) ---------- Forwarded message ---------- Date: Sun, 1 Mar 1998 17:35:31 -0700 (MST) From: ROOT <[EMAIL PROTECTED]> To: Dean Gaudet <[EMAIL PROTECTED]> Subject: Re: os-linux/1893: Server halts for apparently no reason It is package glibc-2.0.6-8 for i386. It is RedHat 5.0 ---------- Forwarded message ---------- Date: Sun, 1 Mar 1998 17:54:38 -0700 (MST) From: ROOT <[EMAIL PROTECTED]> To: Dean Gaudet <[EMAIL PROTECTED]> Subject: Re: os-linux/1893: Server halts for apparently no reason Yes. This is the server. btw, I have had a lot of SYN flood warnings in dmesg... a LOT! ---------- Forwarded message ---------- Date: Sun, 1 Mar 1998 17:55:12 -0700 (MST) From: ROOT <[EMAIL PROTECTED]> To: Dean Gaudet <[EMAIL PROTECTED]> Subject: Re: os-linux/1893: Server halts for apparently no reason No, I run my own 2.0.33. I told you in my previous message that SYN floods are abundant. ---------- Forwarded message ---------- Date: Sun, 1 Mar 1998 17:56:02 -0700 (MST) From: ROOT <[EMAIL PROTECTED]> To: Dean Gaudet <[EMAIL PROTECTED]> Subject: Re: os-linux/1893: Server halts for apparently no reason I built apache myself, and have the PHP and frontpage patches on it. I don't normally send any signals to my server, but a kill -1 pid gets the server back up. ---------- Forwarded message ---------- Date: Sun, 1 Mar 1998 17:57:46 -0700 (MST) From: ROOT <[EMAIL PROTECTED]> To: Dean Gaudet <[EMAIL PROTECTED]> Subject: Re: os-linux/1893: Server halts for apparently no reason Here is my whole config file! : # -FrontPage- version=2.0 # This is the main server configuration file. See URL # http://www.apache.org/ # for instructions. # Do NOT simply read the instructions in here without understanding # what they do, if you are unsure consult the online docs. You have been # warned. # Originally by Rob McCool # ServerType is either inetd, or standalone. ServerType standalone # If you are running from inetd, go to "ServerAdmin". # Port: The port the standalone listens to. For ports < 1023, you will # need httpd to be run as root initially. Port 80 # HostnameLookups: Log the names of clients or just their IP numbers # e.g. www.apache.org (on) or 204.62.129.132 (off) HostnameLookups on # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # User/Group: The name (or #number) of the user/group to run httpd as. # On SCO (ODT 3) use User nouser and Group nogroup User nobody Group nobody # ServerAdmin: Your address, where problems with the server should be # e-mailed. ServerAdmin [EMAIL PROTECTED] # ServerRoot: The directory the server's config, error, and log files # are kept in ServerRoot /etc/httpd # BindAddress: You can support virtual hosts with this option. This option # is used to tell the server which IP address to listen to. It can either # contain "*", an IP address, or a fully qualified Internet domain name. # See also the VirtualHost directive. #BindAddress "*" # ErrorLog: The location of the error log file. If this does not start # with /, ServerRoot is prepended to it. ErrorLog logs/error_log # TransferLog: The location of the transfer log file. If this does not # start with /, ServerRoot is prepended to it. TransferLog logs/access_log #AgentLog logs/agent_log #RefererLog logs/referer_log # PidFile: The file the server should log its pid to PidFile logs/httpd.pid # ScoreBoardFile: File used to store internal server process information ScoreBoardFile logs/apache_status # ServerName allows you to set a host name which is sent back to clients for # your server if it's different than the one the program would get (i.e. use # "www" instead of the host's real name). # # Note: You cannot just invent host names and hope they work. The name you # define here must be a valid DNS name for your host. If you don't understand # this, ask your network administrator. ServerName www.wipd.com # CacheNegotiatedDocs: By default, Apache sends Pragma: no-cache with each # document that was negotiated on the basis of content. This asks proxy # servers not to cache the document. Uncommenting the following line disables # this behavior, and proxies will be allowed to cache the documents. #CacheNegotiatedDocs # Timeout: The number of seconds before receives and sends time out # n.b. the compiled default is 1200 (20 minutes !) Timeout 400 #BrowserMatch Mozilla/2 nokeepalive # KeepAlive: The number of Keep-Alive persistent requests to accept # per connection. Set to 0 to deactivate Keep-Alive support #KeepAlive On #MaxKeepAliveRequests 100 KeepAlive 5 # KeepAliveTimeout: Number of seconds to wait for the next request KeepAliveTimeout 15 # Server-pool size regulation. Rather than making you guess how many # server processes you need, Apache dynamically adapts to the load it # sees --- that is, it tries to maintain enough server processes to # handle the current load, plus a few spare servers to handle transient # load spikes (e.g., multiple simultaneous requests from a single # Netscape browser). # It does this by periodically checking how many servers are waiting # for a request. If there are fewer than MinSpareServers, it creates # a new spare. If there are more than MaxSpareServers, some of the # spares die off. These values are probably OK for most sites --- MinSpareServers 10 MaxSpareServers 20 # Number of servers to start --- should be a reasonable ballpark figure. StartServers 10 # Limit on total number of servers running, i.e., limit on the number # of clients who can simultaneously connect --- if this limit is ever # reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW. # It is intended mainly as a brake to keep a runaway server from taking # Unix with it as it spirals down... MaxClients 150 # MaxRequestsPerChild: the number of requests each child process is # allowed to process before the child dies. # The child will exit so as to avoid problems after prolonged use when # Apache (and maybe the libraries it uses) leak. On most systems, this # isn't really needed, but a few (such as Solaris) do have notable leaks # in the libraries. MaxRequestsPerChild 30 # Proxy Server directives. Uncomment the following line to # enable the proxy server: ProxyRequests On # To enable the cache as well, edit and uncomment the following lines: #CacheRoot /home/httpd/proxy #CacheSize 5 #CacheGcInterval 4 #CacheMaxExpire 24 #CacheLastModifiedFactor 0.1 #CacheDefaultExpire 1 #NoCache adomain.com anotherdomain.edu joes.garage.com # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, in addition to the default. See also the VirtualHost command Listen 8001 Listen 80 #Listen 12.34.56.78:80 # VirtualHost: Allows the daemon to respond to requests for more than one # server address, if your server machine is configured to accept IP packets # for multiple addresses. This can be accomplished with the ifconfig # alias flag, or through kernel patches like VIF. # Any httpd.conf or srm.conf directive may go into a VirtualHost command. # See alto the BindAddress entry. [lots of vhosts removed -djg]
