just brew it! wrote:Gah! That's ridiculous.Ahh, OK. Didn't realize your distro renamed the Apache process... the canonical name for the server process is httpd.
Personal computing discussed
Moderators: renee, SecretSquirrel, notfred
bitvector wrote:How can red hat rename httpd to httpd? It's already named that!just brew it! wrote:Ahh, OK. Didn't realize your distro renamed the Apache process... the canonical name for the server process is httpd
Actually, jbi, it's Red Hat that renames it to httpd. Almost all of the others (Debian-derived, Gentoo, etc.) will have it as apache2.
mattsteg wrote:How can red hat rename httpd to httpd? It's already named that!
bitvector wrote:My strong preference is that executables not be renamed. It leads to crap confusion like this (although it's perhaps sorta understandable in this case). What's wrong with only renaming the package and leaving the filenames intact to the maximum degree possible. At least they could include the original name so that grep etc. would find the right process when searching for it.mattsteg wrote:How can red hat rename httpd to httpd? It's already named that!
I forgot the apache source builds as httpd unmodified (so probably Slackware and the BSDs will also have it as httpd).
What's odd about Red Hat's packaging is that they actually call the package httpd. So if you want to install apache, you install the httpd package. Since there are other httpd's, many distros pass the configure option (--with-program-name=apache2 or some variation) to make it less generic than the default.
mattsteg wrote:bitvector wrote:My strong preference is that executables not be renamed. It leads to crap confusion like this (although it's perhaps sorta understandable in this case). What's wrong with only renaming the package and leaving the filenames intact to the maximum degree possible. At least they could include the original name so that grep etc. would find the right process when searching for it.mattsteg wrote:How can red hat rename httpd to httpd? It's already named that!
I forgot the apache source builds as httpd unmodified (so probably Slackware and the BSDs will also have it as httpd).
What's odd about Red Hat's packaging is that they actually call the package httpd. So if you want to install apache, you install the httpd package. Since there are other httpd's, many distros pass the configure option (--with-program-name=apache2 or some variation) to make it less generic than the default.
You'd think they could at least have the sense to call it apache2-httpd or something.
just brew it! wrote:...and IMO lack of consistency like this is one of the things that scares a lot of people away from Linux.
mattsteg wrote:You'd think they could at least have the sense to call it apache2-httpd or something.
titan wrote:At least with programs it's "supposed" to be that way, even if it's a crappy practice. My beef is that you should be able to use the applications docs for as much as possible if needed, and changing names etc. really gets in the way of that.Distro's aren't the only one guilty of this, but individual programs as well.
# This is a modification of the default Apache 2.2 configuration file
# for Gentoo Linux.
#
# Support:
# http://www.gentoo.org/main/en/lists.xml [mailing lists]
# http://forums.gentoo.org/ [web forums]
# irc://irc.freenode.net#gentoo-apache [irc chat]
#
# Bug Reports:
# http://bugs.gentoo.org [gentoo related bugs]
# http://httpd.apache.org/bug_report.html [apache httpd related bugs]
#
#
# 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 "var/log/apache2/foo.log"
# with ServerRoot set to "/usr" will be interpreted by the
# server as "/usr/var/log/apache2/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 "/usr/lib/apache2"
# 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
#
# GENTOO: Automatically defined based on apache2-builtin-mods at compile time
#
# The following modules are considered as the default configuration.
# If you wish to disable one of them, you may have to alter other
# configuration directives.
#
# Change these at your own risk!
LoadModule userdir_module modules/mod_userdir.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
<IfDefine CACHE>
LoadModule cache_module modules/mod_cache.so
</IfDefine>
LoadModule cgi_module modules/mod_cgi.so
<IfDefine DAV>
LoadModule dav_module modules/mod_dav.so
</IfDefine>
<IfDefine DAV>
LoadModule dav_fs_module modules/mod_dav_fs.so
</IfDefine>
<IfDefine DAV>
LoadModule dav_lock_module modules/mod_dav_lock.so
</IfDefine>
LoadModule dbd_module modules/mod_dbd.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
<IfDefine CACHE>
LoadModule disk_cache_module modules/mod_disk_cache.so
</IfDefine>
LoadModule env_module modules/mod_env.so
LoadModule expires_module modules/mod_expires.so
LoadModule ext_filter_module modules/mod_ext_filter.so
<IfDefine CACHE>
LoadModule file_cache_module modules/mod_file_cache.so
</IfDefine>
LoadModule filter_module modules/mod_filter.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
<IfDefine INFO>
LoadModule info_module modules/mod_info.so
</IfDefine>
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
<IfDefine CACHE>
LoadModule mem_cache_module modules/mod_mem_cache.so
</IfDefine>
LoadModule mime_module modules/mod_mime.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
<IfDefine PROXY>
LoadModule proxy_module modules/mod_proxy.so
</IfDefine>
<IfDefine PROXY>
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
</IfDefine>
<IfDefine PROXY>
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
</IfDefine>
<IfDefine PROXY>
LoadModule proxy_connect_module modules/mod_proxy_connect.so
</IfDefine>
<IfDefine PROXY>
LoadModule proxy_http_module modules/mod_proxy_http.so
</IfDefine>
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule speling_module modules/mod_speling.so
<IfDefine SSL>
LoadModule ssl_module modules/mod_ssl.so
</IfDefine>
<IfDefine INFO>
LoadModule status_module modules/mod_status.so
</IfDefine>
<IfDefine SUEXEC>
LoadModule suexec_module modules/mod_suexec.so
</IfDefine>
LoadModule unique_id_module modules/mod_unique_id.so
<IfDefine USERDIR>
LoadModule userdir_module modules/mod_userdir.so
</IfDefine>
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
# 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
# Supplemental configuration
#
# Most of the configuration files in the /etc/apache2/modules.d/ directory can
# be turned on using APACHE2_OPTS in /etc/conf.d/apache2 to add extra features
# or to modify the default configuration of the server.
#
# To know which flag to add to APACHE2_OPTS, look at the first line of the
# the file, which will usually be an <IfDefine OPTION> where OPTIONS is the
# flag to use.
Include /etc/apache2/modules.d/*.conf
# Virtual-host support
#
# Gentoo has made using virtual-hosts easy. In /etc/apache2/vhosts.d/ we
# include a default vhost (enabled by adding -D DEFAULT_VHOST to
# APACHE2_OPTS in /etc/conf.d/apache2).
Include /etc/apache2/vhosts.d/*.conf
# vim: ts=4 filetype=apache
#Name of host
ServerName 192.168.1.4:80
SSLDisable
#Protect / from everyone and .htaccess
UserDir disabled root
<Directory />
Order Deny,Allow
Deny from all
AllowOverride None
</Directory>
DocumentRoot "/home/media/www"
DirectoryIndex "index.html"
#Allow access to www
<Directory "/home/media/www">
Order Deny,Allow
Allow from all
</Directory>
<Directory "/home/media/pub">
Order Deny,Allow
Allow from all
</Directory>
#<VirtualHost 192.168.1.4:80>
#ServerName 192.168.1.4:80
#DocumentRoot "/home/media/www"
#CustomLog logs/mydomain_access_log combined
#ErrorLog logs/mydomain_error_log
#ErrorDocument 401 /auth.html
#</VirtualHost>
# /etc/conf.d/apache2: config file for /etc/init.d/apache2
# When you install a module it is easy to activate or deactivate the modules
# and other features of apache using the APACHE2_OPTS line. Every module should
# install a configuration in /etc/apache2/modules.d. In that file will be an
# <IfDefine NNN> where NNN is the option to enable that module.
# Here are the options available in the default configuration:
#
# CACHE Enables mod_cache
# MEM_CACHE Enables default configuration mod_mem_cache
# DAV Enables mod_dav
# DEFAULT_VHOST Enables name-based virtual hosts, with the default
# virtual host being in /var/www/localhost/htdocs
# ERRORDOCS Enables default error documents for many languages.
# INFO Enables mod_info, a useful module for debugging
# LANGUAGE Enables content-negotiation based on language and charset.
# LDAP Enables mod_ldap (available if USE=ldap)
# AUTH_LDAP Enables authentication through mod_ldap (available if USE=ldap)
# MANUAL Enables /manual/ to be the apache manual (available if USE=docs)
# PROXY Enables mod_proxy
# SSL Enables SSL (available if USE=ssl)
# SSL_DEFAULT_VHOST Enables default vhost for SSL (you should enable this
# when you enable SSL unless you know what you are doing)
# SUEXEC Enables running CGI scripts (in USERDIR) through suexec.
# USERDIR Enables /~username mapping to /home/username/public_html
#
# Warning: You need one of DEFAULT_VHOST or SSL_DEFAULT_VHOST, otherwise apache
# will not listen for incomming connections on any port.
#The following line was the original default
#APACHE2_OPTS="-D DEFAULT_VHOST -D INFO -D LANGUAGE -D MANUAL -D SUEXEC"
APACHE2_OPTS="-D INFO -D LANGUAGE -D MANUAL -D SUEXEC"
# Extended options for advanced uses of Apache ONLY
# You don't need to edit these unless you are doing crazy Apache stuff
# As not having them set correctly, or feeding in an incorrect configuration
# via them will result in Apache failing to start
# YOU HAVE BEEN WARNED.
# ServerRoot setting
SERVERROOT=/usr/lib/apache2
# Configuration file location
# - If this does NOT start with a '/', then it is treated relative to
# $SERVERROOT by Apache
CONFIGFILE=/etc/apache2/httpd.conf
# Location to log startup errors to
# They are normally dumped to your terminal.
STARTUPERRORLOG="/var/log/apache2/startuperror.log"
# A command that outputs a formatted text version of the HTML at the URL
# of the command line. Designed for lynx, however other programs may work.
#LYNX="lynx -dump"
# The URL to your server's mod_status status page.
# Required for status and fullstatus
STATUSURL="http://localhost/server-status"
# Method to use when reloading the server
# Valid options are 'restart' and 'graceful'
# See http://httpd.apache.org/docs/2.2/stopping.html for information on
# what they do and how they differ.
RELOAD_TYPE="restart"
[Wed Oct 10 16:09:32 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Oct 10 16:09:33 2007] [notice] Digest: generating secret for digest authentication ...
[Wed Oct 10 16:11:25 2007] [notice] Digest: done
[Wed Oct 10 16:11:26 2007] [notice] Apache/2.2.6 (Unix) configured -- resuming normal operations
192.168.1.2 - - [10/Oct/2007:16:11:26 -0500] "GET / HTTP/1.1" 200 -
192.168.1.2 - - [10/Oct/2007:16:18:11 -0500] "GET / HTTP/1.1" 200 -
192.168.1.2 - - [10/Oct/2007:16:19:59 -0500] "GET /index.html HTTP/1.1" 200 -
notfred wrote:Apache shouldn't need the files executable, just readable by the user that the apache process (whatever it is called ) is running as. The directory typically needs the execute flag on because on directories that doesn't mean execute but instead allows you to list the directory (if I remember correctly).
notfred wrote:The directory typically needs the execute flag on because on directories that doesn't mean execute but instead allows you to list the directory (if I remember correctly).
titan wrote:Is that something to do with the directories losing their executableness?
find . -type f -print0 | xargs -0 chmod a-x
find . -type d -print0 | xargs -0 chmod a+x
titan wrote:On a side note, I was totally tempted to run with a light weight web server like Boa, lighttpd, or thttpd. Thing is, they have horrible documentation, if any. On top of that, some haven't been updated in years.
titan wrote:Now, on to the next thing. How do I make it so my grandma can make postings?
notfred wrote:Thanks JBI and bitvector. I knew directories were funny and didn't have time to check, guess my memory was in the right direction but not perfect.
titan wrote:I am constantly surprised at Linux's ability to do complex tasks with relatively simple commands.
find . -type f -print0 | xargs -0 chmod a-x
find . -type f -exec chmod a-x \{\} \;
titan wrote:I am constantly surprised at Linux's ability to do complex tasks with relatively simple commands.
The connection was reset
The connection to the server was reset while the page was loading.
* The site could be temporarily unavailable or too busy. Try again in a few moments.
* If you are unable to load any pages, check your computer's network connection.
* If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
Internet Explorer cannot display the webpage
Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.
What you can try:
Diagnose Connection Problems
More information
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.