Apache 1.3.37 + PHP 5.2.2 CGI + More

Wieso nimmst Du nicht erst einmal Sqlite? SQL ist ein Standard, viele RDBMS sind weitgehend kompatibel. Was kann MySQL, das Sqlite nicht kann und das Du unbedingt bräuchtest, dazu noch auf der Fritz!Box? Nur weil Du vielleicht MySQL schon einmal benutzt hast und den Namen kennst, bedeutet das ja nicht zwangsweise, daß Du Dein Ziel mit einer anderen Datenbank nicht auch erreichen könntest. Einen LAMP-Stack auf der FB laufen zu lassen, ist sicher leicht gesagt und hört sich "einfach" an, aber im Grunde willst Du einfach einen Webserver, eine Skriptsprache und ein RDBMS. Da gibt es diverse Kombinationen, die infrage kommen, nicht nur die eine, an welche Du denkst. Du möchtest ein fachliches Problem lösen und benötigst dazu technische Hilfsmittel. Es führen für Dich evtl. mehr Wege nach Rom als nur der, der Dir zuerst einfällt. :)
 
Hi,
egal ob ich Apache oder minihttpd nehme, wenn ich starten will kommt folgende Fehlermeldung:

line1:syntax error: word unexpected (expecting ") ")
 
[GELÖST] ./apache: can't resolve symbol '__eqsf2'

Hallo zusammen,

bekomme obige Fehlermeldung im apache_error_log (apache läuft ansonsten), wenn ich http://fritz.box:85/ aufrufe.

Hat jemand ne Idee, googlen und SuFu waren erfolglos :-(

Danke!

EDIT: Fehler lag in der Pfadangabe für htdocs, habe nun den absoluten Pfad genommen.
 
Zuletzt bearbeitet:
ALso habe nach einer kleinen Pause das ganze jetzt nochmal probiert. WEnn ich apache starten will kommt:
apache: could not open document config file apache-1.3.37/conf/apache.conf

chmod 755 apache.conf
und chmod +x apache.conf bringen keine Abhilfe.

Ich habe das alles auf der Box ohne USB am laufen!

edit: Das Problem habe ich gelöst, wenn ich apache als root laufen lassen will kommt ne kritische Fehlermeldung, dass das verboten ist. Wie ist denn der Befehl, dass ich neue Benutzer und Gruppen anlegen kann?

edit2: So das Problem von oben habe ich jetzt auch gelöst, hab mich einfach mal schlau gemacht wie man über den vi gruppen und benutzer in linux anlegt.
Jetzt kommt folgende Meldung, mit der weis ich jetzt wirklich nichts mehr anzufangen:

fopen: No such file or directory
apache: could not open error log file /var/tmp/apache-1.3.37/apache-1.3.37/logs/apache_error_log.

Die 2. Zeile kann ich ja noch verstehen, es gibt kein logs verzeichnis muss man das selber anlegen?
aber was des fopen bedeutet kapier ich net??

edit x^^: tschuldigung ich frag zu viel das root verzeichnis war falsch eingestellt ,)


editxx: So endlich läuft der Apache!!
Nur wie kann ich es machen, dass er permanent eingebunden wird? Also nach stromausfall und neustart ist ja die var/tmp wieder leer??
 
Zuletzt bearbeitet:
hallo,

ich möchte mein apache updaten auf php 5.2.2 und mit sql (lite). ich habe es nach der anleitung installiert mit dem kleinen unterschied: portfreigabe habe ich direkt in ar7.cfg und nicht über zusätzliches netzwerkinterface realisiert. apache mit php läuft schon (evtl siehe link).

was muss ich dazu tun?
 
@Keen
theoretisch: ja
praktisch: schwierig
problem(unter anderem): MySQL ab 3.23.xx (Empfohlen: 4.1.1 oder neuer)
ich kenne noch keine möglichkeit, mysql-server auf der box zu installieren

@all
würde mich auch interessieren wegen z.b. mediawiki! hat sie schon einer vielleicht drauf?
für mediawiki fehlt mir MySQL und PostgreSQL, dazu siehe am besten bild
 

Anhänge

  • mediawiki.jpg
    mediawiki.jpg
    52 KB · Aufrufe: 75
Sehr schade das es nicht geht, könnte es denn auf der neuen Fritz Box laufen?
 
Sehr schade das es nicht geht, könnte es denn auf der neuen Fritz Box laufen?

finde ich auch schade! allerdings ist "es geht nicht" der falsche ausdruck: da muss ein profi ran - richtig ausprobieren, testen. mir fehlen leider noch die kenntnisse dazu. neue/alte box ist daher glaub ich nicht das problem :???:
 
Vielleicht schaut sich die Sache mal ein Profi an;)
 
GD Lib auf der Fritzbox

Hi,
ich habe auf meiner 7170 den Apache mit PHP laufen. Funzt auch super.
Jetzt frage ich mich, ob es für die Fritzbox auch die PHP Extension gd-lib gibt.
Es gibt da nämlich PHP Guestbooks mit Spamschutz. Die blenden dann eine "verunstaltete" Nummer ein, die man abtippen muß. Dafür brauchts wohl diese GD-Lib.
Kann irgendjemand helfen ?

Gruss
Magic Roomy
 
php: can't resolve symbol 'mblen'

Moin!

Nachdem ich dachte, dass bei mir nun alles sauber läuft, enttäuscht mich mein Apache mit dieser Meldung (im Titel) im error.log.

Die Suchfunktion hier brachte nur ein Ergebnis, nämlich dass kein Zugriff aufs tmp-Verzeichnis vermutlich der Grund sein könnte. Google war aucvh nicht grad mein Freund.

Ich habe versuchsweise meine php.ini so modifiziert, dass sessions in einem eigenen Verzeichnis abgelegt werden, aber dennoch Fehlanzeige. Auch der in diesem Forum empfohlene Symlink funzt nicht (/tmp -> /var/tmp)

Derzeit habe ich auf meiner FB mit 2.6er Kernel den Apachen 1.3.37 und php 5.5.2 im Einsatz. Hat jemand einen heissen Tipp für mich?

Gruß webbie / Germany
 
can't resolve symbol 'mblen'

Schade, dass keiner der alten Hasen hier Rat weiß....
die Meldung
Code:
can't resolve symbol 'mblen'
versauert mir nach wie vor so ziemlich alles. Kaum ein CMS etc will seinen Dienst verrichten... :(
 
CMS / Wiki auf FritzBox

Hallo Leute,
ich will euch nicht die Stimmung vermiesen, aber der Einsatz eines Wikis auf der FB wird schon allein an der Prozesserleistung scheitern. Wenn ihr euch davon selbst überzeugen wollt, probierts doch erstmal mit einem Wiki auf Filebasis, dann habt ihr das DB-gehample nicht mehr (siehe http://en.wikipedia.org/wiki/Comparison_of_wiki_software). Ich selbst hatte mal MoinMoin auf der FB laufen, aber selbst primitivste Seiten, ob von intern oder extern aufgerufen, machten wirklich keinen Spaß.

Jimmy81
 
Hallo Jimmy81
Ich denk ja nicht mal im entferntesten an eine Anbindung per mysql etc.
Mein PHP meldet den Fehler bei den einfachsten CMS, die man sich so filebasierend vorstellen kann...
Gruß
webbie - Germany
 
Hallo Leute,
ich will euch nicht die Stimmung vermiesen, aber der Einsatz eines Wikis auf der FB wird schon allein an der Prozesserleistung scheitern. Wenn ihr euch davon selbst überzeugen wollt, probierts doch erstmal mit einem Wiki auf Filebasis, dann habt ihr das DB-gehample nicht mehr (siehe http://en.wikipedia.org/wiki/Comparison_of_wiki_software). Ich selbst hatte mal MoinMoin auf der FB laufen, aber selbst primitivste Seiten, ob von intern oder extern aufgerufen, machten wirklich keinen Spaß.

Jimmy81

stimmt nicht ganz...

Hallo Jimmy81
Ich denk ja nicht mal im entferntesten an eine Anbindung per mysql etc.
Mein PHP meldet den Fehler bei den einfachsten CMS, die man sich so filebasierend vorstellen kann...
Gruß
webbie - Germany
richtig: mysql vergessen wir! ich habe schon einige wiki's ausprobiert. das einzige, was gut läuft ist "PWP Wiki Processor". dazu siehe hier und wenn ihr nichts dagegen habt, würde ich die diskussion auch dorthin "verlegen". dieses thread soll sich meiner meinung nach mit problemen bei apache installation beschäftigen.

dokuwiki sollte auch gehen, habe ich aber nicht zum laufen gebracht.
außerdem habe ich schon ein login-system für pwp entwickelt (mit sqlite, aber auch ohne möglich), falls es mal jemand braucht... aber wie gesagt: würde ich hier weiter besprechen.

gruß
 
...und wenn ihr nichts dagegen habt, würde ich die diskussion auch dorthin "verlegen". dieses thread soll sich meiner meinung nach mit problemen bei apache installation beschäftigen...

Ich will nicht unhöflich erscheinen, aber die Rede vom Wiki kam erstmalig durch Jimmy81 auf und wurde dann von Dir fortgeführt. Mein Problem bezieht und bezog sich ausschließlich auf die eingeschränkte PHP-Funktionalität nach meiner Apache-Installation. Ich erwähnte nur die mangelnde Funktionalität an Hand meines CMS (wobei ein CMS etwas anderes als ein Wiki ist).
Also möchte ich gern die Diskussion hier fortführen und den Schwerpunkt auf fehlende Funktionalitäten des Apachen in Verbindung mit PHP legen und mich nicht über Wiki und Co unterhalten.. es sei denn, Du hast dort die Lösung des Problems für mich parat :)

Gruß
webbie - Germany

Nachtrag: Inzwischen stellte ich fest, dass als CMS die Freeware von artmedic in der Version 3.5 problemlos zu laufen scheint. Offenbar werden bei den anderen getesteten Versionen zu hohe Anforderungen gestellt, die unserer kleiner Freund in der Box nicht bewältigen kann.
 
Zuletzt bearbeitet:
Hallo!

Also, ich habe Apache mit PHP von hier: http://deefrag.dyndns.org/
Ich habe das Verzeichnis htdocs mit .htaccess geschützt, weiterhin das directory listing aktiviert.
Funktioniert auch soweit. Nur wenn ich jetzt einen zweiten User in die .htpasswd eintrage kann ich mich nicht mehr einloggen, weder mit dem ersten noch mit dem 2. User...
Hat da jemand eine Idee, woran das liegen kann, oder wo ich noch Einstellungen vornehmen muss? (access.conf, apache.conf ?)
Die Einstellungen für das directory listing waren auch nicht so einfach, funktioniert bisher nur unter der angehängten Config und dem Eintrag in der .htaccess, ...

.htaccess:
Code:
AuthType Basic
AuthName "Tom's Apache Webserver"
AuthUserFile /var/media/ftp/USBFlashMemory-Partition-0-0/apache/htdocs/.htpasswd
Require valid-user
Options +Indexes

access.conf:

Code:
##
## access.conf -- Apache HTTP server configuration file
##

#
# This is the default file for the AccessConfig directive in apache.conf.
# It is processed after apache.conf and srm.conf.
#
# To avoid confusion, it is recommended that you put all of your
# Apache server directives into the apache.conf file and leave this
# one essentially empty.
#

apache.conf:
Code:
##
## apache.conf -- Apache HTTP server configuration file
##

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/> for detailed information about
# the directives.
#
# 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.
#
# After this file is processed, the server will look for and process
# apache-1.3.37/conf/srm.conf and then apache-1.3.37/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# 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 "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone.  Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
#
ServerRoot "/var/media/ftp/USBFlashMemory-Partition-0-0/apache"

#
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
#
#LockFile /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this.  But if yours does (you'll know because
# this file will be  created when you run Apache) then you *must* ensure that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache.scoreboard

#
# In the standard configuration, the server will process apache.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order.  The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults.  You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig /var/media/ftp/USBFlashMemory-Partition-0-0/apache/conf/srm.conf
#AccessConfig /var/media/ftp/USBFlashMemory-Partition-0-0/apache/conf/access.conf

#
# 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 5
MaxSpareServers 10

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 5

#
# 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 setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
#       request per connection. For example, if a child process handles
#       an initial request and 10 subsequent "keptalive" requests, it
#       would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 192.168.178.100:85

#
# BindAddress: You can support virtual hosts with this option. This directive
# 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> and Listen directives.
#
#BindAddress *

#
# 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.
# Please read the file http://httpd.apache.org/docs/dso.html for more
# details about the DSO mechanism and run `httpd -l' for the list of already
# built-in (statically linked and thus always available) modules in your httpd
# binary.
#
# Note: The order in which modules are loaded is important.  Don't change
# the order below without expert advice.
#
# Example:
# LoadModule foo_module libexec/mod_foo.so

#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On

### Section 2: '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.
#

#
# If your ServerType directive (set earlier in the 'Global Environment'
# section) is set to "inetd", the next few directives don't have any
# effect since their settings are defined by the inetd configuration.
# Skip ahead to the ServerAdmin directive.
#

#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 85

#
# 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".
#  . On HPUX you may not be able to use shared memory as nobody, and the
#    suggested workaround is to create a user www and use that user.
#  NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
#  when the value of (unsigned)Group is above 60000;
#  don't use Group "#-1" on these systems!
#
User ftpuser
Group root

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

#
# 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.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
#
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#
ServerName fritz.box

#
# 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/media/ftp/USBFlashMemory-Partition-0-0/apache/htdocs

#
# 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
# permissions.
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
</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 "/var/media/ftp/USBFlashMemory-Partition-0-0/apache/htdocs">

#
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
    Options FollowSymLinks

#
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
#
    AllowOverride All

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

#
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
#
<IfModule mod_userdir.c>
    UserDir public_html
</IfModule>

#
# Control access to UserDir directories.  The following is an example
# for a site where these directories are restricted to read-only.
#
#<Directory /home/*/public_html>
#    AllowOverride FileInfo AuthConfig Limit
#    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#    <Limit GET POST OPTIONS PROPFIND>
#        Order allow,deny
#        Allow from all
#    </Limit>
#    <LimitExcept GET POST OPTIONS PROPFIND>
#        Order deny,allow
#        Deny from all
#    </LimitExcept>
#</Directory>

#
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index.  Separate multiple entries with spaces.
#
<IfModule mod_dir.c>
    DirectoryIndex index.html
</IfModule>

#
# AccessFileName: The name of the file to look for in each directory
# for access control information.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess files from being viewed by
# Web clients.  Since .htaccess files often contain authorization
# information, access is disallowed for security reasons.  Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files.  If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
#
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</Files>

#
# 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

#
# UseCanonicalName:  (new for 1.3)  With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name.  With this setting off, Apache will
# use the hostname:port that the client supplied, when possible.  This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
#
UseCanonicalName On

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
<IfModule mod_mime.c>
    TypesConfig /var/media/ftp/USBFlashMemory-Partition-0-0/apache/conf/mime.types
</IfModule>

#
# DefaultType is 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

#
# 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.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
#
<IfModule mod_mime_magic.c>
    MIMEMagicFile /var/media/ftp/USBFlashMemory-Partition-0-0/apache/conf/magic
</IfModule>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# 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 /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache_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

#
# 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
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# 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 /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache_access_log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache_referer_log referer
#CustomLog /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache_agent_log agent

#
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog /var/media/ftp/USBFlashMemory-Partition-0-0/apache/logs/apache_access_log combined

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of:  On | Off | EMail
#
ServerSignature On

# EBCDIC configuration:
# (only for mainframes using the EBCDIC codeset, currently one of:
# Fujitsu-Siemens' BS2000/OSD, IBM's OS/390 and IBM's TPF)!!
# The following default configuration assumes that "text files"
# are stored in EBCDIC (so that you can operate on them using the
# normal POSIX tools like grep and sort) while "binary files" are
# stored with identical octets as on an ASCII machine.
#
# The directives are evaluated in configuration file order, with
# the EBCDICConvert directives applied before EBCDICConvertByType.
#
# If you want to have ASCII HTML documents and EBCDIC HTML documents
# at the same time, you can use the file extension to force
# conversion off for the ASCII documents:
# > AddType       text/html .ahtml
# > EBCDICConvert Off=InOut .ahtml
#
# EBCDICConvertByType  On=InOut text/* message/* multipart/*
# EBCDICConvertByType  On=In    application/x-www-form-urlencoded
# EBCDICConvertByType  On=InOut application/postscript model/vrml
# EBCDICConvertByType Off=InOut */*


#
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
#
<IfModule mod_alias.c>

    #
    # Note that if you include a trailing / on fakename then the server will
    # require it to be present in the URL.  So "/icons" isn't aliased in this
    # example, only "/icons/".  If the fakename is slash-terminated, then the
    # realname must also be slash terminated, and if the fakename omits the
    # trailing slash, the realname must also omit it.
    #
    Alias /icons/ "/var/media/ftp/USBFlashMemory-Partition-0-0/apache/icons/"

    <Directory "/var/media/ftp/USBFlashMemory-Partition-0-0/apache/icons">
        Options Indexes MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

    # This Alias will project the on-line documentation tree under /manual/
    # even if you change the DocumentRoot. Comment it if you don't want to
    # provide access to the on-line documentation.
    #
    Alias /manual/ "/var/media/ftp/USBFlashMemory-Partition-0-0/apache/htdocs/manual/"

    <Directory "/var/media/ftp/USBFlashMemory-Partition-0-0/apache/htdocs/manual">
        Options Indexes FollowSymlinks MultiViews
        AllowOverride None
        Order allow,deny
        Allow from all
    </Directory>

    #
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the realname 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/media/ftp/USBFlashMemory-Partition-0-0/apache/cgi-bin/"

Action php-script /cgi-bin/php
AddHandler php-script .php

    #
    # "apache-1.3.37/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    #
    <Directory "/var/media/ftp/USBFlashMemory-Partition-0-0/apache/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>

</IfModule>
# End of aliases.

#
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Format: Redirect old-URI new-URL
#

#
# Directives controlling the display of server-generated directory listings.
#
<IfModule mod_autoindex.c>

    #
    # FancyIndexing is whether you want fancy directory indexing or standard
    #
    IndexOptions FancyIndexing

    #
    # AddIcon* directives tell the server which icon to show for different
    # files or filename extensions.  These are only displayed for
    # FancyIndexed directories.
    #
    AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

    AddIconByType (TXT,/icons/text.gif) text/*
    AddIconByType (IMG,/icons/image2.gif) image/*
    AddIconByType (SND,/icons/sound2.gif) audio/*
    AddIconByType (VID,/icons/movie.gif) video/*

    AddIcon /icons/binary.gif .bin .exe
    AddIcon /icons/binhex.gif .hqx
    AddIcon /icons/tar.gif .tar
    AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
    AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
    AddIcon /icons/a.gif .ps .ai .eps
    AddIcon /icons/layout.gif .html .shtml .htm .pdf
    AddIcon /icons/text.gif .txt
    AddIcon /icons/c.gif .c
    AddIcon /icons/p.gif .pl .py
    AddIcon /icons/f.gif .for
    AddIcon /icons/dvi.gif .dvi
    AddIcon /icons/uuencoded.gif .uu
    AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
    AddIcon /icons/tex.gif .tex
    AddIcon /icons/bomb.gif core

    AddIcon /icons/back.gif ..
    AddIcon /icons/hand.right.gif README
    AddIcon /icons/folder.gif ^^DIRECTORY^^
    AddIcon /icons/blank.gif ^^BLANKICON^^

    #
    # DefaultIcon is which icon to show for files which do not have an icon
    # explicitly set.
    #
    DefaultIcon /icons/unknown.gif

    #
    # AddDescription allows you to place a short description after a file in
    # server-generated indexes.  These are only displayed for FancyIndexed
    # directories.
    # Format: AddDescription "description" filename
    #
    #AddDescription "GZIP compressed document" .gz
    #AddDescription "tar archive" .tar
    #AddDescription "GZIP compressed tar archive" .tgz

    #
    # ReadmeName is the name of the README file the server will look for by
    # default, and append to directory listings.
    #
    # HeaderName is the name of a file which should be prepended to
    # directory indexes.
    #
    ReadmeName README.html
    HeaderName HEADER.html

    #
    # IndexIgnore is a set of filenames which directory indexing should ignore
    # and not include in the listing.  Shell-style wildcarding is permitted.
    #
    IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

</IfModule>
# End of indexing directives.

#
# Document types.
#
<IfModule mod_mime.c>

    #
    # AddLanguage allows you to specify the language of a document. You can
    # then use content negotiation to give a browser a file in a language
    # it can understand.
    #
    # Note 1: The suffix does not have to be the same as the language
    # keyword --- those with documents in Polish (whose net-standard
    # language code is pl) may wish to use "AddLanguage pl .po" to
    # avoid the ambiguity with the common suffix for perl scripts.
    #
    # Note 2: The example entries below illustrate that in quite
    # some cases the two character 'Language' abbreviation is not
    # identical to the two character 'Country' code for its country,
    # E.g. 'Danmark/dk' versus 'Danish/da'.
    #
    # Note 3: In the case of 'ltz' we violate the RFC by using a three char
    # specifier. But there is 'work in progress' to fix this and get
    # the reference data for rfc1766 cleaned up.
    #
    # Danish (da) - Dutch (nl) - English (en) - Estonian (ee)
    # French (fr) - German (de) - Greek-Modern (el)
    # Italian (it) - Korean (kr) - Norwegian (no) - Norwegian Nynorsk (nn)
    # Portugese (pt) - Luxembourgeois* (ltz)
    # Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cs)
    # Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
    # Russian (ru)
    #
    AddLanguage da .dk
    AddLanguage nl .nl
    AddLanguage en .en
    AddLanguage et .ee
    AddLanguage fr .fr
    AddLanguage de .de
    AddLanguage el .el
    AddLanguage he .he
    AddCharset ISO-8859-8 .iso8859-8
    AddLanguage it .it
    AddLanguage ja .ja
    AddCharset ISO-2022-JP .jis
    AddLanguage kr .kr
    AddCharset ISO-2022-KR .iso-kr
    AddLanguage nn .nn
    AddLanguage no .no
    AddLanguage pl .po
    AddCharset ISO-8859-2 .iso-pl
    AddLanguage pt .pt
    AddLanguage pt-br .pt-br
    AddLanguage ltz .lu
    AddLanguage ca .ca
    AddLanguage es .es
    AddLanguage sv .sv
    AddLanguage cs .cz .cs
    AddLanguage ru .ru
    AddLanguage zh-TW .zh-tw
    AddCharset Big5         .Big5    .big5
    AddCharset WINDOWS-1251 .cp-1251
    AddCharset CP866        .cp866
    AddCharset ISO-8859-5   .iso-ru
    AddCharset KOI8-R       .koi8-r
    AddCharset UCS-2        .ucs2
    AddCharset UCS-4        .ucs4
    AddCharset UTF-8        .utf8

    # LanguagePriority allows you to give precedence to some languages
    # in case of a tie during content negotiation.
    #
    # Just list the languages in decreasing order of preference. We have
    # more or less alphabetized them here. You probably want to change this.
    #
    <IfModule mod_negotiation.c>
        LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv tw
    </IfModule>

    #
    # AddType allows you to tweak mime.types without actually editing it, or to
    # make certain files to be certain types.
    #
    AddType application/x-tar .tgz

    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    # Despite the name similarity, the following Add* directives have nothing
    # to do with the FancyIndexing customization directives above.
    #
    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 command (see below)
    #
    # If you want to use server side includes, or CGI outside
    # ScriptAliased directories, uncomment the following lines.
    #
    # To use CGI scripts:
    #
    #AddHandler cgi-script .cgi

    #
    # To use server-parsed HTML files
    #
    #AddType text/html .shtml
    #AddHandler server-parsed .shtml

    #
    # Uncomment the following line to enable Apache's send-asis HTTP file
    # feature
    #
    #AddHandler send-as-is asis

    #
    # If you wish to use server-parsed imagemap files, use
    #
    #AddHandler imap-file map

    #
    # To enable type maps, you might want to use
    #
    #AddHandler type-map var

</IfModule>
# End of document types.

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# MetaDir: specifies the name of the directory in which Apache can find
# meta information files. These files contain additional HTTP headers
# to include when sending the document
#
#MetaDir .web

#
# MetaSuffix: specifies the file name suffix for the file containing the
# meta information.
#
#MetaSuffix .meta

#
# Customizable error response (Apache style)
#  these come in three flavors
#
#    1) plain text
#ErrorDocument 500 "The server made a boo boo.
#  n.b.  the single leading (") marks it as text, it does not get output
#
#    2) local redirects
#ErrorDocument 404 /missing.html
#  to redirect to local URL /missing.html
#ErrorDocument 404 /cgi-bin/missing_handler.pl
#  N.B.: You can redirect to a script or a document using server-side-includes.
#
#    3) external redirects
#ErrorDocument 402 http://www.example.com/subscription_info.html
#  N.B.: Many of the environment variables associated with the original
#  request will *not* be available to such a script.

#
# Customize behaviour based on the browser
#
<IfModule mod_setenvif.c>

    #
    # The following directives modify normal HTTP response behavior.
    # The first directive disables keepalive for Netscape 2.x and browsers that
    # spoof it. There are known problems with these browser implementations.
    # The second directive is for Microsoft Internet Explorer 4.0b2
    # which has a broken HTTP/1.1 implementation and does not properly
    # support keepalive when it is used on 301 or 302 (redirect) responses.
    #
    BrowserMatch "Mozilla/2" nokeepalive
    BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0

    #
    # The following directive disables HTTP/1.1 responses to browsers which
    # are in violation of the HTTP/1.0 spec by not being able to grok a
    # basic 1.1 response.
    #
    BrowserMatch "RealPlayer 4\.0" force-response-1.0
    BrowserMatch "Java/1\.0" force-response-1.0
    BrowserMatch "JDK/1\.0" force-response-1.0

</IfModule>
# End of browser customization directives

#
# Allow server status reports, with the URL of http://servername/server-status
# Change the ".example.com" to match your domain to enable.
#
#<Location /server-status>
#    SetHandler server-status
#    Order deny,allow
#    Deny from all
#    Allow from .example.com
#</Location>

#
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".example.com" to match your domain to enable.
#
#<Location /server-info>
#    SetHandler server-info
#    Order deny,allow
#    Deny from all
#    Allow from .example.com
#</Location>

#
# There have been reports of people trying to abuse an old bug from pre-1.1
# days.  This bug involved a CGI script distributed as a part of Apache.
# By uncommenting these lines you can redirect these attacks to a logging
# script on phf.apache.org.  Or, you can record them yourself, using the script
# support/phf_abuse_log.cgi.
#
#<Location /cgi-bin/phf*>
#    Deny from all
#    ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
#</Location>

### Section 3: Virtual Hosts
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at <URL:http://www.apache.org/docs/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
#NameVirtualHost *:80

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
#<VirtualHost *:80>
#    ServerAdmin [email protected]
#    DocumentRoot /www/docs/dummy-host.example.com
#    ServerName dummy-host.example.com
#    ErrorLog logs/dummy-host.example.com-error_log
#    CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost>


Auf meiner Box ist kein Freetz Mod installiert, alles funktioniert soweit wunderbar.
 
PHP mit GD

Hallo,

Dein Forum ist sehr interessant. Ich habe ein Gehäuse moviecube EMTEC-und php-5.2.2-libxml-zlib-sqlite-mipsel.tar.bz2 funktioniert sehr gut. Aber für eine Web-Fotoalbum, es fehlt der GD-lib. Der moviecube nicht Compiler. Können Sie erneut php-5.2.2-libxml-zlib-sqlite-mipsel.tar.bz2 mit GD lib, bitte?
Danke

Bogy
http://www.mhdworld.com/index.php?lang=english / fr.mhdworld.com
 
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.