funjay 发表于 2006-8-11 19:44:03

http://localhost/

阿帕器 装好以后,起动后 输入
http://localhost/
提示:You don't have permission to access / on this server.

我的httpd。con
echo "#
# This is the main Apache HTTP server configuration file.It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.They're here only as hints or reminders.If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/home/shu/forum/Apache" will be interpreted by the
# server as "/home/shu/forum/Apache/logs/foo.log".

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/home/shu/forum/Apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#

<IfModule !mpm_netware_module>
#
# 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.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.This address appears on some server-generated pages, such
# as error documents.e.g. [email protected]
#
ServerAdmin [email protected]

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80
ServerName localhost
#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/home/shu/forum/www"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options Indexes Includes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/home/shu/forum/www">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes Includes FollowSymLinks MultiViews

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride ALL

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.htm index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    </FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog logs/access_log common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog logs/access_log combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/home/shu/forum/Apache/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "/home/shu/forum/Apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/home/shu/forum/Apache/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    AddType application/x-httpd-php .php
    AddType application/x-httpd-php-source .phps

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files.This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
";

funjay 发表于 2006-8-11 19:45:24

而且
/home/shu/forum/www这个目录下 有文件!index。html

dogking 发表于 2006-8-11 20:10:38

权限问题。把你的www里那个文件夹加上其他用户访问的权限 :wink:

funjay 发表于 2006-8-11 21:45:25

都加过的www是我用shu用户新建的
而且conf中已经 指向www文件夹了

KDE 发表于 2006-8-12 06:58:48

登录 shu 账户,在 /home/shu/forum/Apache/ 创建一个 index.htm 或者 index.php 里面写上你的介绍文字。然后执行 chmod -R 755 /home/shu/forum/Apache 再看看能不能访问了?

jiangtao9999 发表于 2006-8-12 16:25:21

你的 apache 用的是哪个用户?
apache 还是 nobody 还是 shu ????

Crossa 发表于 2006-8-13 12:10:59

你怎么安装apache的?
有没有装载WEB DAV??如果装载的话。用户的目录就不能访问了。设了权限也没有用,我实验过。
而且对于用户目录的访问2.0.55以后的版本,多少都有点小麻烦
把下面的注释去掉。修改conf/extra/httpd-vhosts.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

修改conf/extra/httpd-vhosts.conf
用虚拟主机的方式配置你的站点!将

<Directory "/home/shu/forum/Apache/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>


还原成原先的值。
不要将你的 web根目录设置成用户的目录,不然会不能访问的



配置完apache

janus_le 发表于 2006-8-14 00:03:06

我以前在Debian遇到相似问题的。ROOT下不能访问,但是以普通用户登录就可以了。你试试吧

Crossa 发表于 2006-8-14 10:38:55

楼上的,我用普通用户,也不能访问

funjay 发表于 2006-8-14 15:32:11

装apache是用root装的,访问我是用普通用户访问的
root起动apache的,提示:
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName


普通用户起动不了,提示:
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

root下也不能访问的,

funjay 发表于 2006-8-14 16:15:19

这是我阿帕奇下的error日志
[Mon Aug 14 15:15:35 2006] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 14 15:15:35 2006] [notice] Digest: done
[Mon Aug 14 15:15:35 2006] [notice] Apache/2.2.3 (Unix) configured -- resuming normal operations
[Mon Aug 14 15:15:55 2006] [notice] caught SIGTERM, shutting down
[Mon Aug 14 15:21:10 2006] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 14 15:21:10 2006] [notice] Digest: done
[Mon Aug 14 15:21:10 2006] [notice] Apache/2.2.3 (Unix) configured -- resuming normal operations
[Mon Aug 14 15:21:29 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:37 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:38 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:39 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:40 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:41 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:42 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:21:42 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:22:27 2006] [notice] caught SIGTERM, shutting down
[Mon Aug 14 15:24:21 2006] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 14 15:24:21 2006] [notice] Digest: done
[Mon Aug 14 15:24:21 2006] [notice] Apache/2.2.3 (Unix) configured -- resuming normal operations
[Mon Aug 14 15:24:30 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:24:33 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:24:55 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:25:02 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:25:02 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:28:12 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:28:13 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:28:19 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:31:40 2006] [notice] caught SIGTERM, shutting down
[Mon Aug 14 15:34:27 2006] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 14 15:34:27 2006] [notice] Digest: done
[Mon Aug 14 15:34:27 2006] [notice] Apache/2.2.3 (Unix) configured -- resuming normal operations
[Mon Aug 14 15:34:31 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:32 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:32 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:33 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:33 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:33 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:33 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:34 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:35 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:36 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:36 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:37 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:38 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:38 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:34:39 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:35:33 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:35:34 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:35:37 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:36:48 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:36:48 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:42:37 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:42:38 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:42:38 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:42:39 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:42:39 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 15:43:36 2006] [notice] caught SIGTERM, shutting down
[Mon Aug 14 15:45:59 2006] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 14 15:45:59 2006] [notice] Digest: done
[Mon Aug 14 15:45:59 2006] [notice] Apache/2.2.3 (Unix) configured -- resuming normal operations
[Mon Aug 14 15:46:05 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Mon Aug 14 16:08:20 2006] [notice] caught SIGTERM, shutting down
[Mon Aug 14 16:10:21 2006] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 14 16:10:21 2006] [notice] Digest: done
[Mon Aug 14 16:10:21 2006] [notice] Apache/2.2.3 (Unix) configured -- resuming normal operations
[Mon Aug 14 16:10:26 2006] [crit] [client 127.0.0.1] (13)Permission denied: /home/shu/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable



/home/shu/.htaccess .我没有这个文件!在shu下面

qdzhuang 发表于 2006-8-16 16:15:39

<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    </FilesMatch>


Deny from all->Allow from all

funjay 发表于 2006-8-16 23:54:54

it is not ok

qdzhuang 发表于 2006-8-17 09:26:15

/home/shu/.htaccess 你放在/home/shu???,权限问题
页: [1]
查看完整版本: http://localhost/