[Frage] Wie Freetz-Programme starten? (Tags: enable external processing, *.external Datei)

jeffy

Neuer User
Mitglied seit
23 Apr 2011
Beiträge
17
Punkte für Reaktionen
0
Punkte
0
Hallo Freetz-Gemeinde!

Meine FB 7170:
Code:
/var # cat /proc/version 
Linux version 2.6.13.1-ohio (2895) (gcc-Version 3.4.6) #1 Wed Jan 27 13:20:43 CET 2010

Nachdem ich über "make menuconfig" zwei Dateien

Code:
jeffy@localhost freetz-1.1.4]$ ll images/7170_04.80freetz-1.1.4.de_20110423*
-rw-r--r--. 1 jeffy jeffy 1812480 2011-04-23 12:58 images/7170_04.80freetz-1.1.4.de_20110423-125822.external
-rw-r--r--. 1 jeffy jeffy 8192000 2011-04-23 12:58 images/7170_04.80freetz-1.1.4.de_20110423-125822.image


erhalten habe und sie erfolgreich auf meine FB installiert habe, möchte ich nun die Programme

Code:
[jeffy@localhost freetz-1.1.4]$ ll packages/
total 48
drwxr-xr-x. 7 jeffy jeffy 4096 2011-04-23 12:33 apache-1.3.41
drwxr-xr-x. 3 jeffy jeffy 4096 2011-02-11 22:59 avm-firewall-2.0.4_rc2
drwxr-xr-x. 3 jeffy jeffy 4096 2011-04-10 21:47 bash-3.2.48
drwxr-xr-x. 3 jeffy jeffy 4096 2011-04-10 21:47 fstyp-0.1
drwxr-xr-x. 3 jeffy jeffy 4096 2011-04-23 14:00 fuse-2.7.4
drwxr-xr-x. 3 jeffy jeffy 4096 2011-04-10 21:47 haserl-0.9.25
drwxr-xr-x. 3 jeffy jeffy 4096 2011-02-11 22:59 mc-4.6.1
drwxr-xr-x. 3 jeffy jeffy 4096 2011-04-10 21:47 modcgi-0.3
drwxr-xr-x. 3 jeffy jeffy 4096 2011-04-23 14:02 ntfs-2009.4.4
drwxr-xr-x. 3 jeffy jeffy 4096 2011-02-11 22:59 php-5.2.10
drwxr-xr-x. 3 jeffy jeffy 4096 2011-02-11 22:59 syslogd-cgi-0.2.3
drwxr-xr-x. 3 jeffy jeffy 4096 2011-02-11 22:59 vim-7.1

benutzen bzw. starten.

1. ausgelagerte Programme starten

Meine ausgelagerten Dateien sehen direkt auf der FB, verbunden über telnet, so aus (= Ergebnis des *.external Uploads):

Code:
/var/mod/root # ls -ahl /var/media/ftp/uStor01/external/bin/
-rwxrwxrwx    1 root     root       620.0k Apr 11 12:28 bash
/var/mod/root # ls -ahl /var/media/ftp/uStor01/external/usr/bin/
-rwxrwxrwx    1 root     root       530.0k Apr 23 12:33 mc.bin
-rwxrwxrwx    1 root     root       604.4k Apr 23 12:52 vim

Was muss ich tun, damit ich die drei ausgelagerten Programme ausführen kann, um folgende Fehler zu vermeiden?:

Code:
/var # /var/media/ftp/uStor01/external/bin/bash 
/var/media/ftp/uStor01/external/bin/bash: can't load library 'libreadline.so.5'
/var # /var/media/ftp/uStor01/external/usr/bin/vim 
/var/media/ftp/uStor01/external/usr/bin/vim: can't load library 'libncurses.so.5'
/var # /var/media/ftp/uStor01/external/usr/bin/mc.bin 
/var/media/ftp/uStor01/external/usr/bin/mc.bin: can't load library 'libglib-1.2.so.0'

Wie muss ich die ausgelagerten, auf meinem USB Stick befindlichen Binaries in die FB integrieren, damit sie ausführbar werden? Ich dachte, Freetz macht das automatisch über symbolische Links (= Ergebnis des *.image Uploads)?

2. Die restlichen Programme starten

Nachdem ich die Datei *.image auf die FB hochgeladen habe, kann ich keine der für mich wichtigen Programme, über "make menuconfig" selektiert, auf der FB finden. Muss ich die Ordner unter

Code:
[jeffy@localhost packages]$ pwd
/home/jeffy/programs/freetz-1.1.4/packages

manuell auf den USB Stick kopieren und sie dann manuell starten (z.B. "/var/media/ftp/uStor01/manually_copied/apache -f ./conf/apache.conf")? Warum sehe ich in der Freetz-GUI den Dienst "syslogd-cgi" nicht? Muss ich noch einen symbolischen Link auf meiner FB erstellen und auf den USB Stick zeigen?

3. Zusatz

Warum sollte ich mir die Appache/PHP Version von z.B. http://www.ip-phone-forum.de/showthread.php?t=127089&highlight=apache+-f+conf oder http://www.xobztirf.de/selfsite.php?aktion=Apache%20und%20PHP wählen, wenn mir Freetz doch eine eigene Appache/PHP Version anbietet?

Danke!

P.S.: Anbei noch das Ergebnis vom Hochladen meiner beiden Dateien:

-> I. *.external Upload:

Code:
[external] Processing file /var/tmp/dBLcf8
[external] Target directory: /var/media/ftp/uStor01/external
[external] killall: .external mc.bin vim bash
[external] Removing old stuff
[external] Unpacking new stuff:
  ./
  ./.external
  ./usr/
  ./usr/bin/
  ./usr/bin/mc.bin
  ./usr/bin/vim
  ./bin/
  ./bin/bash
[external] Done.

-> II. *.image Upload:

Code:
AVM-Dienste anhalten, Teil 1 (prepare_fwupgrade start) ...
  cat: can't open '/var/run/delayed_reboot.pid': No such file or directory
  rm: cannot remove '/var/run/delayed_reboot.pid': No such file or directory
  rmmod: rfcntl: No such file or directory
  killall: flashd: no process killed
  killall: minid: no process killed
  disable watchdog
  rmmod: isdn_fbox_fon3: No such file or directory
  rmmod: kdsldmod: Resource temporarily unavailable
  killall: checkservices: no process killed
ERLEDIGT

Firmware-Archiv extrahieren ...
  ./
  ./var/
  ./var/install
  ./var/tmp/
  ./var/tmp/filesystem.image
  ./var/tmp/kernel.image
  ./var/.config
  ./var/.packages
  ./var/flash_update.o
  ./var/regelex
  ./var/static.pkg
  ./var/signature
  ./var/chksum
  ./var/flash_update.ko
  ./var/info.txt
DONE

AVM-Dienste anhalten, Teil 2 (prepare_fwupgrade end) ...
  cat: can't open '/var/run/delayed_reboot.pid': No such file or directory
  rm: cannot remove '/var/run/delayed_reboot.pid': No such file or directory
  ifconfig: SIOCGIFFLAGS: No such device
  ifconfig: SIOCGIFFLAGS: No such device
  ifconfig: SIOCGIFFLAGS: No such device
  ifconfig: SIOCGIFFLAGS: No such device
  ifconfig: SIOCGIFFLAGS: No such device
  ifconfig: SIOCGIFFLAGS: No such device
  rmmod: tiap: No such file or directory
  disable watchdog
ERLEDIGT

Ausführen des Firmware-Installationsskripts /var/install ...
  install: have Kernel 2.6
  install: check and install new firmware ...
  /bin/update_led_on: line 2: can't create /dev/led: No such device or address
  OEM=1und1
  ANNEX=B
  testing acceptance for device Fritz_Box_7170 ...
  korrekt install type: ar7_8MB_xilinx_4eth_3ab_isdn_nt_te_pots_wlan_usb_host_25762
  device has installtype ar7_8MB_xilinx_4eth_3ab_isdn_nt_te_pots_wlan_usb_host_25762
  assumed ANNEX B -- found ANNEX B
  device has ANNEX B
  OK - OEM 1und1 is supported
  OK - accept this update for device Fritz_Box_7170 ...
  testing acceptance for device Fritz_Box_7170 done
  curr: 29.04.80  new: xx.04.80
  debug: curr: 29.04.80
  debug: new: "XX.04.80"
  major_currFWver=29
  middle_currFWver=4
  minor_currFWver=80
  middle_newFWver=4
  minor_newFWver=80
  check Firmware Version: xx.04.80
  DEBUG: 4 >= 4
  DEBUG: 80 >= 80
  Accept Firmware Version: xx.04.80
  install: 26 check files...
  File already contains the checksum, verifying
  Calculated checksum is 7D9D69DD
  Saved checksum is 7D9D69DD
  Checksum validation successful!
  chksum for file /var/tmp/kernel.image ok
  install: 26 getting mtd to install...
  install: -----------------------------------------------------
  bootloader_size 0x00010000
  jffs2_size 0x00070000
  Kernel_without_jffs2_size 7340032
  kernel_image_size 7409928
  kernel_mtd_size 7798784
  Kernel_Start_Add=268500992
  Kernel_End_Addr=275910920
  Kernel_without_jffs2_End_Addr=275841024
  install: Image would overlap - jffs2 will be deleted ...
  install: -----------------------------------------------------
  install: kernel_size=7798784
  install: kernel_update_start=268500992
  install: kernel_update_len=7798784
  install: 26 setting files to install...
  install: /var/tmp/kernel.image to start(268500992) size(7798784)
  install: check for old settings ...
  set INFO led to blink (modul=7, state=4)
  /bin/update_led_on: line 2: can't create /dev/led: No such device or address
ERLEDIGT - Rückgabewert des Installationsskripts = 1 (INSTALL_SUCCESS_REBOOT)

Von /var/post_install generierter Inhalt:
  #! /bin/sh
  echo $0: start
  sleep 1
  killall run_clock
  if ps | grep -v grep | grep -q telefon ; then killall telefon ; fi
  if ps | grep -v grep | grep -q telnetd ; then killall telnetd ; fi
  echo skip deleting language from env
  echo MODE=update > /dev/avm_power
  echo "disable" > /dev/watchdog
  echo still running:
  ps
  lsmod
  sleep 1
  update_parameter=flash_update_file0="/var/tmp/kernel.image,268500992,7798784,crc=1"
  insmod /var/flash_update.ko $update_parameter
  exit 0
ENDE DER DATEI

Das Nach-Installationsskript läuft beim Neutart (reboot) und führt die
darin definiterten Aktionen aus, z.B. das tatsächliche Flashen der Firmware.
Sie können immer noch entscheiden, diesen Vorgang abzubrechen, indem Sie
das Skript und den Rest der extrahierten Firmware-Komponenten löschen.
 
Nachdem ich die Datei *.image auf die FB hochgeladen habe, kann ich keine der für mich wichtigen Programme, über "make menuconfig" selektiert, auf der FB finden. Muss ich die Ordner unter
...
Hast Du die "*.image-" und "*.external-Dateien" hochgeladen oder geflasht?
 
Laut

Das Nach-Installationsskript läuft beim Neutart (reboot) und führt die
darin definiterten Aktionen aus, z.B. das tatsächliche Flashen der Firmware

habe ich erst einen Upload und dann einen Restart meiner FB durchgeführt, d.h. Upload dauerte so 3 min, dann habe ich gewartet bis das Ergebnis vom Hochladen kam und dann habe ich den Stecker gezogen und die FB wieder gestartet.

Wie flashe ich etwas? Oder wie bringe ich meine neues Firmware Image vom RAM in den Flash-Chip?
 
Poste mal Screenshots vom "upload" der .image- und der .external-Datei. Reboot der Box macht man mit der Schaltfläche "Neustart" und nicht durch "Stecker ziehen".
 
Poste mal Screenshots vom "upload" der .image- und der .external-Datei. Reboot der Box macht man mit der Schaltfläche "Neustart" und nicht durch "Stecker ziehen".

Danke SF!

1. Frage ist gelöst!

Das heißt das Hochladen der *.image Datei über die Freetz GUI (Port 81) hat nicht funktioniert (= Flashen geht nicht). Das Hochladen der *.image Datei über die AVM GUI (Port 80) hat funktioniert, weil sie automatisch einen Restart gemacht hat (= Flashen geht). Evtl. muss ich beim Hochladen der *.image Datei über die Freetz GUI noch länger warten (> 3 min), damit automatisch ein Restart gemacht wird.!???

Ich werde zukünftig nur noch über die AVM GUI neue *.image Dateien hochladen, damit das Hochladen und anschließend das Flashen funktioniert (= das Image vom RAM in den Flash-Chip dauerhaft schreiben). Das Hochladen von *.external Dateien mache ich weiter über die Freetz GUI.


Könnte man mir evtl. noch Frage 2 und 3 beantworten (siehe auch oben)?


Zu 2)

Muss ich auf der FB unter

Code:
/ # ls -ahl /var/mod/pkg/
drwxr-xr-x    2 root     root            0 Apr 23 12:54 .
drwxr-xr-x   11 root     root            0 Jan  1  2000 ..
lrwxrwxrwx    1 root     root            1 Jan  1  2000 apache -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 avm-firewall -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 bash -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 fstyp -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 haserl -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 mc -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 modcgi -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 php -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 syslogd -> /
lrwxrwxrwx    1 root     root            1 Jan  1  2000 vim -> /

selber den symbolischen Link auf den Ordner z.B.

Code:
/var/media/ftp/uStor01/manually_copied/

setzen, d.h. ich habe vorher die Inhalte der Ordner

Code:
/home/jeffy/programs/freetz-1.1.4/packages
(z.B. "apache-1.3.41/")

nach

Code:
/var/media/ftp/uStor01/manually_copied/

kopiert?

zu 3)

Ist es OK, wenn ich die Appache/PHP Version von Freetz nehme und nicht die anderen Versionen? Ich denke, dass ich mit der Freetz Version starten sollte, wenn ich keine DBS benötige. Oder?

Vielen Dank!
 
Sorry for the English ...

I cannot really answer your questions, but I can point you to lighttpd in stead of Apache, which is maybe more suitable and better worked out.
 
1. Frage ist gelöst!
...
Ich werde zukünftig nur noch über die AVM GUI neue *.image Dateien hochladen, damit das Hochladen und anschließend das Flashen funktioniert (= das Image vom RAM in den Flash-Chip dauerhaft schreiben). Das Hochladen von *.external Dateien mache ich weiter über die Freetz GUI.

Könnte man mir evtl. noch Frage 2 und 3 beantworten (siehe auch oben)?

Zu 2)

Muss ich auf der FB unter
...
selber den symbolischen Link auf den Ordner z.B.
...
zu 3)

Ist es OK, wenn ich die Appache/PHP Version von Freetz nehme und nicht die anderen Versionen?
Deine 1. Frage ist leider noch nicht gelöst. Ich denke Du hast noch nicht verstanden, wie Du das Freetz-Image flashen sollst.
Deine 2. Frage beantworte ich mit nein (hat auch was mit deiner 1. Frage zu tun).
Zu deiner 3. Frage: Was meinst Du mit "die anderen Versionen"?
 
Mich wundert, dass in deinem ersten Post fehlende Libraries aufgeführt werden, die bei external aber nicht auftauchen. Wo sind die Libs hin verschwunden? Vielleicht ein Problem mit Freetz-1.1.x?

Gruß
Oliver
 
Deine 1. Frage ist leider noch nicht gelöst. Ich denke Du hast noch nicht verstanden, wie Du das Freetz-Image flashen sollst.
Deine 2. Frage beantworte ich mit nein (hat auch was mit deiner 1. Frage zu tun).
Zu deiner 3. Frage: Was meinst Du mit "die anderen Versionen"?

zu 1. *.image Datei: Für die AVM GUI muss ich lange genug warten, bis der Reboot automatisch durch ist (= "Flashen"). Für die Freetz GUI ist es techn. sicherlich aktuell noch nicht gelöst bzw. verstanden. Aber ich kann mit der AVM GUI Lösung leben.

zu 2. Hast Du einen Link/eine Doku/Erklärung, der/die beschreibt, wie ich Programme unter "/home/jeffy/programs/freetz-1.1.4/packages" (z.B. "/home/jeffy/programs/freetz-1.1.4/packages/apache-1.3.41") ausführbar auf die FB bekomme, sie gestartet werden können (unabhängig von der Konfiguration;darüber gibt es Doku genug)?
Oder anders gefragt: Ich verstehe nicht, was der nächste Schritt nach dem Flashen der *.image und *.external Dateien und den erzeugten Ordnern unter "/home/jeffy/programs/freetz-1.1.4/packages" ist. Warum wird das nicht in die *.external Datei gepackt und landet nach dem Hochladen unter "/var/media/ftp/uStor01/external/"? Ich nehme an, dass ich doch manuell die Ordner unter "/home/jeffy/programs/freetz-1.1.4/packages" auf den USB Stick kopieren muss. Mir ist bekannt, dass alle Dateien unter root/ (z.B. "/home/jeffy/programs/freetz-1.1.4/packages/bash-3.2.48/root/bin/bash") in das *.external gehen.

zu 3. Ich meine die beiden oben gennanten Links/Alternativen zu "/home/jeffy/programs/freetz-1.1.4/packages/apache-1.3.41". Anscheinend gibt es Personen, die nicht mit der Appache-Freetz Version arbeiten.

Mich wundert, dass in deinem ersten Post fehlende Libraries aufgeführt werden, die bei external aber nicht auftauchen. Wo sind die Libs hin verschwunden? Vielleicht ein Problem mit Freetz-1.1.x?

Gruß
Oliver

Nachdem ich über die AVM GUI mein *.image hochgeladen habe und ein automatischer Restart der FB stattfand (= "flashen"), gibt es jetzt folgende libs auf der FB:

Code:
/ # find . -name "libreadline*"
./usr/lib/libreadline.so
./usr/lib/libreadline.so.5
./usr/lib/libreadline.so.5.2
/ # find . -name "libncurses*"
./usr/lib/libncurses.so
./usr/lib/libncurses.so.5
./usr/lib/libncurses.so.5.6
/ # find . -name "libglib-*"
./usr/lib/libglib-1.2.so.0
./usr/lib/libglib-1.2.so.0.0.10

Alles OK mit Freetz-1.1.4! Nur fehlt mir in meinem Verständnis noch eine kleine Synapsenverbindung, um zu verstehen, wie das Konzept von "enable external processing" klappt (siehe oben, Antwort an sf3978).
 
...
zu 2. Hast Du einen Link/eine Doku/Erklärung, der/die beschreibt, wie ich Programme unter "/home/jeffy/programs/freetz-1.1.4/packages" (z.B. "/home/jeffy/programs/freetz-1.1.4/packages/apache-1.3.41") ausführbar auf die FB bekomme, sie gestartet werden können (unabhängig von der Konfiguration;darüber gibt es Doku genug)?
Oder anders gefragt: Ich verstehe nicht, was der nächste Schritt nach dem Flashen der *.image und *.external Dateien und den erzeugten Ordnern unter "/home/jeffy/programs/freetz-1.1.4/packages" ist. Warum wird das nicht in die *.external Datei gepackt und landet nach dem Hochladen unter "/var/media/ftp/uStor01/external/"? Ich nehme an, dass ich doch manuell die Ordner unter "/home/jeffy/programs/freetz-1.1.4/packages" auf den USB Stick kopieren muss. Mir ist bekannt, dass alle Dateien unter root/ (z.B. "/home/jeffy/programs/freetz-1.1.4/packages/bash-3.2.48/root/bin/bash") in das *.external gehen.
...
Manuell musst Du nichts auf den Stick kopieren. Externalisiert wird nur das, was Du zum externalisieren ausgewählt hast. Die Links zu den externalisierten binaries, werden automatisch angelegt.
 
Hallo,

Manuell musst Du nichts auf den Stick kopieren. Externalisiert wird nur das, was Du zum externalisieren ausgewählt hast. Die Links zu den externalisierten binaries, werden automatisch angelegt.

Danke für die schnelle Antwort - meine einzige Hilfe!

Warum wird dann nicht PHP ausgelagert (bash, mc, VIM werden ausgelagert)?

Code:
[jeffy@localhost freetz-1.1.4]$ make menuconfig
...

[*]Enable external processing   

[*]Keep subdirectories

[*]Create file for upload   

 external directory (/var/media/ftp/uStor01/external/)  ---> 

---   packages   

[*] bash  

[*] mc  

[ ] ntfs     

[*] PHP

[*] VIM

Apache wird nicht angezeigt, um es auslagen zu können!? Was soll ich dann tun?

Danke!
 
Zuletzt bearbeitet:
...
Apache wird nicht angezeigt, um es auslagen zu können!?
...
Nicht alle binaries können ausgelagert werden. Evtl. ist es nicht sinnvoll, nicht möglich oder der maintainer des Paketes hat es so haben wollen oder was weiss ich warum das so ist, oder ... ...

EDIT:

Wenn die Datei "make/<Paket>/external.in" nicht vorhanden ist, kann nicht ausgelagert (externalisiert) werden.

EDIT2:

Muss es unbedingt apache sein? In bzw. für Freetz gibt es noch andere Webserver, die externalisiert werden können. Z. B. hiawatha oder lighttpd.
 
Zuletzt bearbeitet:
Maybe you missed it, but the generated external file should be uploaded too like the image ... (same screen, link in the right bottom)
 
Nicht alle binaries können ausgelagert werden. Evtl. ist es nicht sinnvoll, nicht möglich oder der maintainer des Paketes hat es so haben wollen oder was weiss ich warum das so ist, oder ... ...

EDIT:

Wenn die Datei "make/<Paket>/external.in" nicht vorhanden ist, kann nicht ausgelagert (externalisiert) werden.

EDIT2:

Muss es unbedingt apache sein? In bzw. für Freetz gibt es noch andere Webserver, die externalisiert werden können. Z. B. hiawatha oder lighttpd.


Nein, es muss nicht Apache sein. Von Deinen forgeschlagenen Komponenten: Was wäre dazu die Komponente für dynamische Seiten? Kennst Du eine Komponentenkonstellation, die ausgelagert werden kann und lauffähig ist (statische und dynamische Seiten)? Obwohl Freetz mir Appache und PHP anbieten, kann ich sie nicht nutzen. Verstehe ich nicht? Danke! Gehe jetzt zur Party... Bis morgen!
 
Zuletzt bearbeitet:
... (same screen, link in the right bottom)
Er will uns ja keine Screenshots zeigen, wie er das gemacht hat.;)

EDIT:
Code:
Obwohl Freetz mir [COLOR="red"]Appache und PHP[/COLOR] anbieten, kann ich sie nicht nutzen
Das verstehe ich nicht. Warum kannst Du diese nicht nutzen?

EDIT2:
Hier kannst Du lesen was hiawatha kann.
 
Zuletzt bearbeitet:
@sf3978: maybe off topic, but hiawatha looks as a good alternative web server to me (never heard of it). I tried to compile 7.4.1 (high urgency update), but I get problems with automake/conf or something. Since you are the mass packet producer ;-) can you take a look at it? I plan to make a WebIF for it.
 
.. mass packet producer ;-) ...
Hehe.;-)
Ja, ich habe auch die Fehlermeldung mit 7.4.1. Ich versuch mal die Ursache zu finden.

EDIT:
Mit dieser Änderung:
Code:
$($(PKG)_BINARIES_BUILD_DIR): $($(PKG)_DIR)/.configured
		$(SUBMAKE1) -C $(HIAWATHA_DIR)

[COLOR="red"]# \
#		LIBS="$(HIAWATHA_LIBS)"[/COLOR]
wird 7.4.1 kompiliert. Jetzt muss ich noch schauen was mit libpthread ist.

EDIT2:
Ja, funktioniert, das binary findet die libpthread:
Code:
root@fritz:/var/media/ftp/uStor01/archiv# ./hiawatha -v
[COLOR="red"]Hiawatha v7.4.1[/COLOR]
Copyright (C) by Hugo Leisink <[email protected]>
Code:
root@fritz:/var/media/ftp/uStor01/archiv# ldd ./hiawatha
        libcrypt.so.0 => /lib/libcrypt.so.0 (0x2aabe000)
        libz.so.1 => /usr/lib/freetz/libz.so.1 (0x2aae2000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2ab05000)
        [COLOR="red"]libpthread.so.0 => /lib/libpthread.so.0 (0x2ab23000)[/COLOR]
        libc.so.0 => /lib/libc.so.0 (0x2ab46000)
        ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x2aaa8000)
Viel Spass beim WEB-IF entwickeln.;)
 
Zuletzt bearbeitet:
Die external-Funktion für php ist in freetz-1.1.x broken, da der Apache anders behandelt wird als alle anderen Pakete. Bitte lies dazu die Hilfe im menuconfig.

Lighttpd ist auch nur im Trunk verfügbar...

Gruß
Oliver
 
Die external-Funktion für php ist in freetz-1.1.x broken, da der Apache anders behandelt wird als alle anderen Pakete. Bitte lies dazu die Hilfe im menuconfig.

Lighttpd ist auch nur im Trunk verfügbar...
Gruß
Oliver

Moin!

Danke/Thank you for the answers!

Ich habe mir gerade den aktuellen Trunk heruntergeladen. Der Compilevorgang läuft gerade. Mal sehen, ob PHP damit richtig ausgelagert wird.

Also muss ich doch den Freetz-Apache manuell auf den USB Stick auslagern:

The config files might need adaption to your personal needs before you decide to either manually deploy the package on a USB disk or stick or copy them into the 'root' directory so as to have them built into your firmware.

Hat jd. einen Vorschlag für die Verzeichnisstruktur für Apache, damit ich das ausgelagerte PHP und den manuell kopierten Apache richtig starten kann?

Gruss und Danke!
 
es geht langsam voran...

Ich habe jetzt das von der Freetz Entwicklungsumgebung erstellte "apache" Verzeichnis

Code:
/home/jeffy/programs/freetz/freetz-trunk/packages/target-mipsel_uClibc-0.9.29/apache-1.3.41

auf den USB Stick

Code:
/var/media/ftp/uStor01/external/opt/apache-1.3.41

manuell über "cp -p" kopiert.

Wenn ich jetzt den Apache starten will, kommt folgende Fehlermeldung:

Code:
root@fritz:/var/media/ftp/uStor01/external/opt/apache-1.3.41# /var/media/ftp/uStor01/external/opt/apache-1.3.41/bin/apache -f /var/media/ftp/uStor01/external/opt/apache-1.3.41/conf/apache.conf
Syntax error on line 332 of /var/media/ftp/uStor01/external/opt/apache-1.3.41/conf/apache.conf:
Invalid command 'Order', perhaps mis-spelled or defined by a module not included in the server configuration

Das habe ich gelöst durch:

Code:
root@fritz:/var/media/ftp/uStor01/external/opt/apache-1.3.41# vi /var/media/ftp/uStor01/external/opt/apache-1.3.41/conf/apache.conf
...
# Example:                                                           
# LoadModule foo_module libexec/mod_foo.so
LoadModule access_module /var/media/ftp/uStor01/external/opt/apache-1.3.41/libexec/mod_access.so 
LoadModule auth_module /var/media/ftp/uStor01/external/opt/apache-1.3.41/libexec/mod_auth.so

Allerdings kommt jetzt die nächste Fehlermeldung:

Code:
root@fritz:/var/media/ftp/uStor01/external/opt/apache-1.3.41#
/var/media/ftp/uStor01/external/opt/apache-1.3.41/bin/apache -f /var/media/ftp/uStor01/external/opt/apache-1.3.41/conf/apache.conf
[B]Segmentation fault[/B]

Ich habe eine statische Kompilierung gewählt. Soll ich es doch dynamisch, also "benutze bitte geshared Libs und generiere keine dedizierten Libs für das apache Programm", bei "make menuconfig" auswählen?
Muss ich noch irgendwelche Pfade setzen oder weitere shared Libs über "make menuconfig" auswählen, damit mein Apache läuft? Ich habe keine Ideen mehr...

Vielen Danke schon mal!

P.S. Anbei noch meine aktuelle 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
# ./conf/srm.conf and then ./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/uStor01/external/opt/apache-1.3.41"

#
# 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 ./logs/apache.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile ./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 ./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 ./conf/srm.conf
#AccessConfig ./conf/access.conf

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

#
# 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 1
MaxSpareServers 6

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

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

#
# 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.1: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 10.0.0.2

#
# 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
LoadModule access_module /var/media/ftp/uStor01/external/opt/apache-1.3.41/libexec/mod_access.so
LoadModule auth_module /var/media/ftp/uStor01/external/opt/apache-1.3.41/libexec/mod_auth.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 8080

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

#
# 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/uStor01/external/opt/apache-1.3.41/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 -Indexes -Includes -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/uStor01/external/opt/apache-1.3.41/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 -Indexes -FollowSymLinks -MultiViews

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

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

<Directory ./cgi-bin>
	Options ExecCGI
	AllowOverride None
</Directory>

ScriptAlias	/cgi-bin/	/var/media/ftp/uStor01/external/opt/apache-1.3.41/cgi-bin/

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

#
# 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.php default.php index.html index.htm default.htm default.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 ./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 ./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 On

#
# 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/uStor01/external/opt/apache-1.3.41/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

#
# 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 ./logs/access.log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog ./logs/apache_referer_log referer
#CustomLog ./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 ./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 Off

# 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/ "./icons/"

    # <Directory "./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/ "./htdocs/manual/"

    # <Directory "./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/ "./cgi-bin/"

    #
    # "./cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    #
    # <Directory "./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.
#
ExtendedStatus On
<Location /server-status>
   SetHandler server-status
   Order deny,allow
   Deny from all
   Allow from 10.0.0.0/255.255.0.0
</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>

Außerdem noch mein aktueller FB Kernel:

Code:
root@fritz:/var/media/ftp/uStor01/external/opt/apache-1.3.41# cat /proc/version 
Linux version 2.6.13.1-ohio (2895) (gcc-Version 3.4.6) #1 Wed Jan 27 13:20:43 CET 2010
 
Zuletzt bearbeitet:
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.