我有一个在 Amazon AWS EC2 中运行的 VPS这篇优秀的文章。
除了 Apache+PHP 不能修改文件（创建日志等）之外，一切都很完美。
所以我按照下面的说明进行操作To fix file permissions for the Apache web server 这里。。
已修复，现在我安装的 PHP 应用程序可以创建文件。
但是，如果我登录并untar在新的虚拟 Web 主机文件夹（即在 下）中备份站点，/var/www/html/myNewSite那么除非我重新运行上述“修复”PHP，否则 PHP 无法再次编辑文件。
我已经检查了 Apache 正在以 ( apache) 的身份运行，并使该用户成为名为 的组的成员www。
www 文件夹如下所示：
drwxrwsr-x 2 root www 4096 Jan 19 16:56 cgi-bin drwxrwsr-x 3 root www 4096 May 3 16:14 error drwxrwsr-x 6 root www 4096 May 7 14:07 html drwxrwsr-x 3 root www 4096 May 3 16:14 icons drwxrwsr-x 2 root www 4096 May 3 16:14 noindex
html网站文件夹下有：
drwxrwsr-x 2 root www 4.0K May 6 11:14 myNewSite
如果我使用以下myNewSite命令解压文件：
tar -zxvf mytar.tar.gz -C .
然后我最终得到这样的文件：
-rwxr-xr-x 1 myUserName www 537 Apr 21 12:27 composer.json -rwxr-xr-x 1 myUserName www 3.5K Apr 21 12:27 CONTRIBUTING.md -rwxr-xr-x 1 myUserName www 12K Apr 21 12:27 htaccess.txt -rwxr-xr-x 1 myUserName www 2.4K Apr 21 12:27 index.php etc
尽管我 ( myUserName) 是我现在的所有者这一事实的成员，但www似乎会扼杀 Apache 写入文件的能力。
我尝试过那些奇特的g+w属性和其他东西，但无济于事：/
当我提交这个问题时，我皱起了眉头，因为我确信我没有解释清楚和/或遗漏了一些东西（事实上，我推迟了询问，因为我没能弄清楚如何简洁地提出这个问题，而且我不会责怪模组杀死了我的问题；如果这太弱而无法站立，请提前抱歉）。
httpd.conf文件是：
#
# 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.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/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 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_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 specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"
#
# 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
#
Include conf.modules.d/*.conf
#
# 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 apache
Group apache
# '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 root@localhost
#
# 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
#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
#
<Directory />
AllowOverride none
Require all denied
</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.
#
#
# 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 "/var/www/html"
#
# Relax access to content within /var/www.
#
<Directory "/var/www">
AllowOverride None
# Allow open access:
Require all granted
</Directory>
# Further relax access to the default document root:
<Directory "/var/www/html">
#
# 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.4/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks
#
# 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.
#
Require all granted
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied
</Files>
#
# 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/ "/var/www/cgi-bin/"
</IfModule>
#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>
<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /etc/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
#
# 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>
#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8
<IfModule mime_magic_module>
#
# 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
</IfModule>
#
# 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 may be 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.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on
# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
# Added by AcB 2017-05-03 per https://www.taniarascia.com/ etc AWS
NameVirtualHost *:80
<VirtualHost *:80>
ServerName localhost
DocumentRoot /var/www/html/000
</VirtualHost>
<VirtualHost *:80>
ServerName www.example.com
ServerAlias example.com *.example.com
DocumentRoot /var/www/html/example
</VirtualHost>
附录 2017-05-12-12:10 PM（美国东部时间）
我还没有弄清楚如何解决这个问题，但我注意到以下几点。
在托管公司运行的传统 VPS（不是 Amazon VPS）上，我登录为theDomainName（即每个域/虚拟主机都有自己的登录名），如果我ls -l看到网站的文件夹是：
drwxr-xr-x 8 theDomainName theDomainName 4096 May 2 11:25 public_html/
其中的文件遵循相同的所有权和组：
drwxr-xr-x 8 theDomainName theDomainName 4096 May 2 11:25 ./
drwx--x--x 15 theDomainName theDomainName 4096 May 12 12:20 ../
-rwxr-xr-x 1 theDomainName theDomainName 537 Apr 21 08:27 composer.json*
-rwxr-xr-x 1 theDomainName theDomainName 3571 Apr 21 08:27 CONTRIBUTING.md*
-rwxr-xr-x 1 theDomainName theDomainName 12225 Apr 21 08:27 htaccess.txt*
-rwxr-xr-x 1 theDomainName theDomainName 2421 Apr 21 08:27 index.php*
-rwxr-xr-x 1 theDomainName theDomainName 47540 Apr 21 08:27 install.php*
etc
但是，Amazon VPS 设置的网站文件夹为：
drwxrwsr-x 6 root www 4096 May 7 14:07 html
一旦我tar提取出来，我就得到了
-rwxr-xr-x 1 myUserName www 537 Apr 21 12:27 composer.json
-rwxr-xr-x 1 myUserName www 3.5K Apr 21 12:27 CONTRIBUTING.md
-rwxr-xr-x 1 myUserName www 12K Apr 21 12:27 htaccess.txt
-rwxr-xr-x 1 myUserName www 2.4K Apr 21 12:27 index.php
etc
因此，这里的一个主要区别是，对于传统 VPS 版本，我登录的用户名owner和group用户名都是相同的，而我的 Amazon VPS 中并非如此。
因此，也许一个更简洁的问题是，我如何模拟传统 VPS 的功能......？
是否是为每个虚拟主机创建一个用户和一个组并以该用户身份登录...？
去尝试一下，尽管我不太确定这是否/为什么可行......
答案1
首先，在 tar archive( tar -tzvf mytar.tar.gz) 中设置哪些权限很重要。但我假设它们是正确的（与实时的相同）。
另外，您似乎正在以普通用户身份提取存档。焦油人 说：
--no-same-permissions
Apply the user's umask when extracting permissions from the archive (default for ordinary users).
有一个保留权限的选项：
-p, --preserve-permissions, --same-permissions
extract information about file permissions (default for superuser)
请注意，作为普通用户，您将无法设置除您有权访问之外的权限（例如，您将无法将文件所有权设置为 root）
所以我想说 - 使用 root 来实现。
还要考虑一下您是否确实需要站点目录中 root 拥有的文件，特别是如果它们应该可由 apache 写入。恕我直言，apache 所有者会更好。