mysql 已经启动 但 却访问不到

由 街舞 在 10-09-2002 09:55 发表:

mysql 已经启动 但 却访问不到

我是MR9。0 安装时 自带了 APACHE 和PHP+MYSQL

我选了 ,但 安装完了没有~~我又在 KDE下安装了

用/usr/bin/safe_mysqld --root=mysql &

启动的 可探镇不显示 :(

http://ing.ecsee.com/php.php

http://ing.ecsee.com/mysqlcpl

是 PHPMYSQLADMIN

我是个玩LINUX没多就的初手 但翻的大部分帖子

不止从和下手 谢谢了请教


由 街舞 在 10-09-2002 10:01 发表:


http://ing.ecsee.com/mysqlcpl/index.php

哦错了


由 北南南北 在 10-09-2002 10:23 发表:


把配制文件发上来,让弟兄们看了再说.多谢


===========================

请弟兄们发帖时要写个好标题,多谢!

===========================

每天以1000KM/H的速度在跑,感觉还是时间不够:(

“西学东渐,洋为中用” + 创造 = ?

linux ppc


由 街舞 在 10-09-2002 10:40 发表:


Main Configuration Section

You really shouldn't change these settings unless you're a guru

ServerType standalone

ServerRoot /etc/httpd

#ServerName localhost

#LockFile /etc/httpd/httpd.lock

PidFile /var/run/httpd.pid

ScoreBoardFile /etc/httpd/httpd.scoreboard

ErrorLog logs/error_log

LogLevel warn

ResourceConfig /dev/null

AccessConfig /dev/null

DocumentRoot /var/www/html

Dynamic Shared Object (DSO) Support

#LoadModule mmap_static_module modules/mod_mmap_static.so

LoadModule env_module modules/mod_env.so

LoadModule config_log_module modules/mod_log_config.so

LoadModule agent_log_module modules/mod_log_agent.so

LoadModule referer_log_module modules/mod_log_referer.so

#LoadModule mime_magic_module modules/mod_mime_magic.so

LoadModule mime_module modules/mod_mime.so

LoadModule negotiation_module modules/mod_negotiation.so

LoadModule status_module modules/mod_status.so

LoadModule info_module modules/mod_info.so

LoadModule includes_module modules/mod_include.so

LoadModule autoindex_module modules/mod_autoindex.so

LoadModule dir_module modules/mod_dir.so

LoadModule cgi_module modules/mod_cgi.so

LoadModule asis_module modules/mod_asis.so

LoadModule imap_module modules/mod_imap.so

LoadModule action_module modules/mod_actions.so

#LoadModule speling_module modules/mod_speling.so

LoadModule userdir_module modules/mod_userdir.so

LoadModule proxy_module modules/libproxy.so

LoadModule alias_module modules/mod_alias.so

LoadModule rewrite_module modules/mod_rewrite.so

LoadModule access_module modules/mod_access.so

LoadModule auth_module modules/mod_auth.so

LoadModule anon_auth_module modules/mod_auth_anon.so

#LoadModule dbm_auth_module modules/mod_auth_dbm.so

#LoadModule db_auth_module modules/mod_auth_db.so

LoadModule digest_module modules/mod_digest.so

#LoadModule cern_meta_module modules/mod_cern_meta.so

LoadModule expires_module modules/mod_expires.so

LoadModule headers_module modules/mod_headers.so

LoadModule usertrack_module modules/mod_usertrack.so

#LoadModule example_module modules/mod_example.so

#LoadModule unique_id_module modules/mod_unique_id.so

LoadModule setenvif_module modules/mod_setenvif.so

1<ifdefine have_php4="">   
2  
3LoadModule php4_module extramodules/libphp4.so   
4  
5</ifdefine>
1<ifdefine have_ssl="">   
2  
3LoadModule ssl_module extramodules/libssl.so   
4  
5</ifdefine>

LoadModule vhost_alias_module modules/mod_vhost_alias.so

Reconstruction of the complete module list from all available modules

(static and shared ones) to achieve correct module execution order.

[WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO]

ClearModuleList

#AddModule mod_mmap_static.c

AddModule mod_env.c

AddModule mod_log_config.c

AddModule mod_log_agent.c

AddModule mod_log_referer.c

#AddModule mod_mime_magic.c

AddModule mod_mime.c

AddModule mod_negotiation.c

AddModule mod_status.c

AddModule mod_info.c

AddModule mod_include.c

AddModule mod_autoindex.c

AddModule mod_dir.c

AddModule mod_cgi.c

AddModule mod_asis.c

AddModule mod_imap.c

AddModule mod_actions.c

#AddModule mod_speling.c

AddModule mod_userdir.c

AddModule mod_proxy.c

AddModule mod_alias.c

AddModule mod_rewrite.c

AddModule mod_access.c

AddModule mod_auth.c

AddModule mod_auth_anon.c

#AddModule mod_auth_dbm.c

#AddModule mod_auth_db.c

AddModule mod_digest.c

#AddModule mod_cern_meta.c

AddModule mod_expires.c

AddModule mod_headers.c

AddModule mod_usertrack.c

#AddModule mod_example.c

#AddModule mod_unique_id.c

AddModule mod_so.c

AddModule mod_setenvif.c

1<ifdefine have_php4="">   
2  
3AddModule mod_php4.c   
4  
5</ifdefine>
1<ifdefine have_ssl="">   
2  
3AddModule mod_ssl.c   
4  
5</ifdefine>

AddModule mod_vhost_alias.c

Global Configuration

We now support multiple apache configurations on the same server. In

common.conf, we put all directives that are common to all implementations

(httpd, httpd-perl, etc.)

Include conf/commonhttpd.conf

IP Address/Port and Proxied configuration section

The APACHEPROXIED setting can be set in /etc/rc.d/init.d/httpd if you

are using a proxy or accelerator, like the Apache-SGI or khttpd, so that

the fast web server serves static content while Apache handles the

cgi or php files

#BindAddress *

1<ifdefine apacheproxied="">   
2  
3Port 8080   
4  
5Listen 8080   
6  
7</ifdefine>
1<ifdefine !apacheproxied="">   
2  
3Port 80   
4  
5Listen 80   
6  
7</ifdefine>

Likewise, we can set apache as the server by default and send perl

requests via ProxyPass to apache-mod_perl. It increases performance

since the perl interpreter is only used for perl and the standard apache

does all the html and image files, with a smaller footprint.

If you install apache and apache-mod_perl, this is the default config.

If you don't want two web servers to use perl, uninstall apache, and

apache-mod_perl will not be proxied.

 1<ifdefine perlproxied="">   
 2  
 3RewriteEngine on   
 4  
 5RewriteRule ^proxy:.* - [F]   
 6  
 7RewriteRule ^(.*\/perl\/.*)$ http://% {HTTP_HOST}:8200$1 [P]   
 8  
 9RewriteRule ^(.*\/cgi-perl\/.*)$ http://% {HTTP_HOST}:8200$1 [P]   
10  
11</ifdefine>

Log configuration Section

#Single logfile with access, agent and referer information

#This is the default, if vlogs are not defined for the main server

CustomLog logs/access_log combined env=!VLOG

#If VLOG is defined in conf/vhosts/Vhost.conf, we use this entry

CustomLog "|/usr/sbin/advxsplitlogfile" vhost env=VLOG

Virtual Hosts

We include different templates for Virtual Hosting. Have a look in the

vhosts directory and modify to suit your needs.

Include conf/vhosts/Vhosts.conf

#Include conf/vhosts/DynamicVhosts.conf

#Include conf/vhosts/VirtualHomePages.conf

Performance settings Section

Timeout: The number of seconds before receives and sends time out.

Timeout 300

KeepAlive: Whether or not to allow persistent connections (more than

one request per connection). Set to "Off" to deactivate.

KeepAlive On

MaxKeepAliveRequests: The maximum number of requests to allow

during a persistent connection. Set to 0 to allow an unlimited amount.

We recommend you leave this number high, for maximum performance.

MaxKeepAliveRequests 100

KeepAliveTimeout: Number of seconds to wait for the next request from the

same client on the same connection.

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. The default values are probably OK for most sites.

MinSpareServers 4

MaxSpareServers 10

Number of servers to start initially --- should be a reasonable ballpark

figure.

StartServers 4

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

the system 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 memory or other resources. On most systems, this

isn't really needed, but a few (such as Solaris) do have notable leaks

in the libraries. For these platforms, set to something like 10000

or so; a

Published At
Categories with 服务器类
Tagged with
comments powered by Disqus