Bug#231452: marked as done (Suggestion: Relative Includes in apache2.conf, and notes on Including linked-to directories)
Your message dated Fri, 6 Feb 2004 18:16:37 + with message-id <[EMAIL PROTECTED]> and subject line Bug#231452: Suggestion: Relative Includes in apache2.conf, and notes on Including linked-to directories has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 6 Feb 2004 17:58:14 + >From [EMAIL PROTECTED] Fri Feb 06 09:58:14 2004 Return-path: <[EMAIL PROTECTED]> Received: from h55n2fls304o851.telia.com (gloomy.localdomain.local) [81.224.231.55] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1ApAF4-0002dQ-00; Fri, 06 Feb 2004 09:58:14 -0800 Received: from localhost ([127.0.0.1]) by gloomy.localdomain.local with esmtp (Exim 3.35 #1 (Debian)) id 1ApAEY-00039T-00 for <[EMAIL PROTECTED]>; Fri, 06 Feb 2004 18:57:42 +0100 Date: Fri, 6 Feb 2004 18:57:42 +0100 (CET) From: =?ISO-8859-1?Q?Bj=F6rn_Wiberg?= <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Suggestion: Relative Includes in apache2.conf, and notes on Including linked-to directories Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_02_01 X-Spam-Level: Package: apache2-common Version: 2.0.48-7 Severity: wishlist Just something that I thought about when reviewing the apache2.conf file: Why not use relative paths for the Include directives, as they are relative to the server root? # Include module configuration: Include /etc/apache2/mods-enabled/*.load Include /etc/apache2/mods-enabled/*.conf =2E..could be written: # Include module configuration: Include mods-enabled/*.load Include mods-enabled/*.conf And: # Include ports listing Include /etc/apache2/ports.conf # Include generic snippets of statements Include /etc/apache2/conf.d =2E..could be written: # Include ports listing Include ports.conf # Include generic snippets of statements Include conf.d Finally: # Include the virtual host configurations: Include /etc/apache2/sites-enabled =2E..could be written: # Include the virtual host configurations: Include sites-enabled My experience is that it is good to use relative paths where possible. Although for clarity, absolute paths may be better. Furthermore, there's always the danger of the allowance of relative paths disappearing in some future version. This for instance happened to the AuthDigestFile and AuthDigestGroupFile directives for mod_digest when I switched from Apache 2.0.48/Win32 to 2.0.48-5 (and up) on Debian, forcing me to use absolute paths for digest authentication files. Anyway, I thought it would be worth a thought. Another interesting thing about Includes that could be worth noticing is that if you try to include a directory, which actually is a symlink to a directory, Apache will complain instead of including all files in the (linked-to) directory. Adding a slash after the directory (link) name takes care of it, and includes all files in the (linked-to) directory. Best regards, Bj=F6rn -- Bj=F6rn Wiberg ([EMAIL PROTECTED]) Homepage: http://bwiberg.dyndns.org/ --- Received: (at 231452-done) by bugs.debian.org; 6 Feb 2004 18:16:39 + >From [EMAIL PROTECTED] Fri Feb 06 10:16:38 2004 Return-path: <[EMAIL PROTECTED]> Received: from mirror.positive-internet.com [80.87.128.67] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1ApAWs-0002xO-00; Fri, 06 Feb 2004 10:16:38 -0800 Received: by mirror.positive-internet.com (Postfix, from userid 1002) id 4D9304354C; Fri, 6 Feb 2004 18:16:37 + (GMT) Date: Fri, 6 Feb 2004 18:16:37 + From: Thom May <[EMAIL PROTECTED]> To: =?iso-8859-1?Q?Bj=F6rn?= Wiberg <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#231452: Suggestion: Relative Includes in apache2.conf, and notes on Including linked-to directories Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> X-Operating-System: Linux/2.6.0-1-686 (i686) User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.de
Bug#231452: Suggestion: Relative Includes in apache2.conf, and notes on Including linked-to directories
Package: apache2-common Version: 2.0.48-7 Severity: wishlist Just something that I thought about when reviewing the apache2.conf file: Why not use relative paths for the Include directives, as they are relative to the server root? # Include module configuration: Include /etc/apache2/mods-enabled/*.load Include /etc/apache2/mods-enabled/*.conf ...could be written: # Include module configuration: Include mods-enabled/*.load Include mods-enabled/*.conf And: # Include ports listing Include /etc/apache2/ports.conf # Include generic snippets of statements Include /etc/apache2/conf.d ...could be written: # Include ports listing Include ports.conf # Include generic snippets of statements Include conf.d Finally: # Include the virtual host configurations: Include /etc/apache2/sites-enabled ...could be written: # Include the virtual host configurations: Include sites-enabled My experience is that it is good to use relative paths where possible. Although for clarity, absolute paths may be better. Furthermore, there's always the danger of the allowance of relative paths disappearing in some future version. This for instance happened to the AuthDigestFile and AuthDigestGroupFile directives for mod_digest when I switched from Apache 2.0.48/Win32 to 2.0.48-5 (and up) on Debian, forcing me to use absolute paths for digest authentication files. Anyway, I thought it would be worth a thought. Another interesting thing about Includes that could be worth noticing is that if you try to include a directory, which actually is a symlink to a directory, Apache will complain instead of including all files in the (linked-to) directory. Adding a slash after the directory (link) name takes care of it, and includes all files in the (linked-to) directory. Best regards, Björn -- Björn Wiberg ([EMAIL PROTECTED]) Homepage: http://bwiberg.dyndns.org/
Bug#231450: PHP5 install through apxs2: missing leading slash in module path
Package: apache2-threaded-dev Version: 2.0.48-7 Other software: PHP 5.0.0b3 and also PHP 5.0.0RC1-dev (2004-02-06 10:30). When installing PHP 5, it calls instdso.sh which in turn calls apxs2 to install the PHP5 SAPI loadable module. However, the resulting path to the module in apache2.conf misses a leading slash (/). Here is the output from PHP5's "make install" (forgive any strange line breaks; they're due to cut-and-paste): gloomy:~/software/php5-200402061030# make install Installing PHP SAPI module: apache2handler /usr/share/apache2/build/instdso.sh SH_LIBTOOL='/usr/bin/libtool' libphp5.la /usr/lib/apache2/modules /usr/bin/libtool --mode=install cp libphp5.la /usr/lib/apache2/modules/ cp .libs/libphp5.so /usr/lib/apache2/modules/libphp5.so cp .libs/libphp5.lai /usr/lib/apache2/modules/libphp5.la libtool: install: warning: remember to run `libtool --finish /root/software/php5-200402061030/libs' chmod 755 /usr/lib/apache2/modules/libphp5.so [activating module `php5' in /etc/apache2/apache2.conf] Installing PHP CLI binary:/usr/local/bin/ Installing PHP CLI man page: /usr/local/man/man1/ Installing PEAR environment: /usr/local/lib/php/ [PEAR] Archive_Tar- already installed: 1.1 [PEAR] Console_Getopt - already installed: 1.2 [PEAR] PEAR - upgraded: 1.3b6 Wrote PEAR system config file at: /usr/local/etc/pear.conf You may want to add: /usr/local/lib/php to your php.ini include_path [PEAR] DB - upgraded: 1.6.0RC1 [PEAR] HTTP - upgraded: 1.2.2 [PEAR] Mail - upgraded: 1.1.2 [PEAR] Net_SMTP - already installed: 1.2.3 [PEAR] Net_Socket - already installed: 1.0.1 [PEAR] XML_Parser - already installed: 1.0.1 [PEAR] XML_RPC- already installed: 1.0.4 Installing build environment: /usr/local/lib/php/build/ Installing header files: /usr/local/include/php/ Installing helper programs: /usr/local/bin/ program: phpize program: php-config program: phpextdist gloomy:~/software/php5-200402061030# Below is the resulting LoadModule directive that gets added to apache2.conf. Notice that I've added a commented dummy LoadModule directive so that apxs2 at all manages to figure out where to place the new LoadModule directive (for more details, see Bug#231134). Notice that the leading slash in /usr/lib/apache2/modules/libphp5.so is missing: # Include module configuration: Include /etc/apache2/mods-enabled/*.load Include /etc/apache2/mods-enabled/*.conf # To give PHP installation a hint on where to add its LoadModule directive #LoadModule dummy_module /usr/lib/apache2/modules/mod_dummy.so LoadModule php5_moduleusr/lib/apache2/modules/libphp5.so # Include all the user configurations: Include /etc/apache2/httpd.conf This of course has to be corrected manually, as any relative path to the LoadModule directive is taken relative to the server root. I hope that the output from PHP5's "make install" will aid you in spotting the error (either in instdso.sh or apxs2). Best regards, Björn -- Björn Wiberg ([EMAIL PROTECTED]) Homepage: http://bwiberg.dyndns.org/
ЭТО МОЖЕТ БЫТЬ ВАЖНО
Эффективная раскрутка и действенная рекламная поддержка Вашего бизнеса: Это работает! Сегодня Вы можете выбрать удобный и действенный вид продвижения товаров или услуг Вашей фирмы через русскоязычную часть Интернета. Это - единовременная рассылка Вашей рекламной информации по выбранной Вами базе электронных адресов. Конкурентные преимущества такой рекламы - это сочетание "индивидуальности" подачи каждому адресату и масштабности распространения информации о Вашей фирме, о предоставляемых товарах и услугах. Именно эти свойства коммерческих рассылок обеспечивают неизменно высокий отклик и гарантируют многократную окупаемость затрат на рекламу такого рода. Со своей стороны, мы гарантируем оперативное выполнение рассылок. С базами электронных адресов работают опытные программисты высочайшего уровня. Статистика RuNet'a показывает, что более 80 процентов клиентов заказывают повторную рассылку - это объективное свидетельство эффективности почтовой электронной рекламы. Узнайте больше 095 721-6-254 Примите решение! (095) 721*62*54
Re: /var/lib/apache/mod-bandwidth world-writable [forwarded]
Hi, On 04 Feb 2004, Fabio Massimo Di Nitto <[EMAIL PROTECTED]> wrote: > >From mod-bandwith source/documentation: > > * 3) Create the following directories with "rwx" permission to everybody : > */tmp/apachebw > */tmp/apachebw/link > */tmp/apachebw/master Thanks for pointing me to the source documentation. But I do not get it at all. Could you please explain why rwx permissions are needed for any user? Why isn't a 770 on www-data sufficient? The only reason I can come up with is an suexec-enabled apache, but that is as far as I know not the default in debian. I'd prefer a more sane default on the write permissions of those directories. If 777 permissions are really necessary in some cases, this should be added to the mod_bandwidth documentation. If you are not sure under what circumstances 777 permissions are required, I'd be willing to investigate further. Thanx Philipp -- Philipp Weis [EMAIL PROTECTED] Freiburg, Germany http://pweis.com/
Bug#231423: marked as done (apache2-doc: multi-language negociation not working - wrong filenames )
Your message dated Fri, 6 Feb 2004 14:52:44 + with message-id <[EMAIL PROTECTED]> and subject line Bug#231423: apache2-doc: multi-language negociation not working - wrong filenames has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 6 Feb 2004 13:50:41 + >From [EMAIL PROTECTED] Fri Feb 06 05:50:41 2004 Return-path: <[EMAIL PROTECTED]> Received: from user.indexdata.dk (cromme) [213.150.43.10] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ap6NU-0001WG-00; Fri, 06 Feb 2004 05:50:40 -0800 Received: from marc by cromme with local (Exim 4.30) id 1Ap6NQ-XG-78; Fri, 06 Feb 2004 14:50:36 +0100 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Marc Cromme <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: apache2-doc: multi-language negociation not working - wrong filenames X-Mailer: reportbug 2.39 Date: Fri, 06 Feb 2004 14:50:36 +0100 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_02_01 X-Spam-Level: Package: apache2-doc Version: 2.0.47-1 Severity: important Tags: patch After installing apache2-doc, the multi-language negociation does not work out of the box in the /var/www/apache2-default/manual directory and it's subdirectories. As far as I can see, it's the wrong filename which makes the problems: for example surfing into http://localhost/apache2-default/manual/index.html gives the output URI: index.html.de Content-Language: de Content-type: text/html; charset=ISO-8859-1 URI: index.html.en Content-Language: en Content-type: text/html; charset=ISO-8859-1 URI: index.html.ja.jis Content-Language: ja Content-type: text/html; charset=ISO-2022-JP URI: index.html.ko.euc-kr Content-Language: ko Content-type: text/html; charset=EUC-KR URI: index.html.ru.koi8-r Content-Language: ru Content-type: text/html; charset=KOI8-r However, renaming index.html to index.var and surfing into (the non-existent) http://localhost/apache2-default/manual/index.html gives the correct language-depending result. This change must be applied to all negociacion files, that is *.html --> *.var in all dirs. I suspect that similar applies to all *.xml files, but I do not know yet. Furthermore, The following wrong file permissions are found in this package: -rwxr-xr-x1 root root 277 Jul 5 2003 urlmapping.html -rwxr-xr-x1 root root18980 May 29 2003 urlmapping.html.en -rwxr-xr-x1 root root20544 May 29 2003 urlmapping.html.ja.jis please check also all these subdirs for the same errors. drwxr-xr-x2 root root 4096 Feb 6 12:44 developer drwxr-xr-x2 root root 4096 Feb 6 12:44 faq drwxr-xr-x2 root root 4096 Feb 6 12:44 howto drwxr-xr-x2 root root 4096 Feb 6 12:44 images drwxr-xr-x2 root root 4096 Feb 6 12:44 misc drwxr-xr-x2 root root12288 Feb 6 12:44 mod drwxr-xr-x2 root root 4096 Feb 6 12:44 platform drwxr-xr-x2 root root 4096 Feb 6 12:44 programs drwxr-xr-x2 root root 4096 Feb 6 12:44 search drwxr-xr-x2 root root 4096 Feb 6 12:44 ssl drwxr-xr-x 10 root root 4096 Feb 6 12:44 style drwxr-xr-x2 root root 4096 Feb 6 12:44 vhosts -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux cromme 2.4.24-1-386 #1 Tue Jan 6 19:18:04 EST 2004 i686 Locale: LANG=C, LC_CTYPE=C -- no debconf information --- Received: (at 231423-done) by bugs.debian.org; 6 Feb 2004 14:52:46 + >From [EMAIL PROTECTED] Fri Feb 06 06:52:46 2004 Return-path: <[EMAIL PROTECTED]> Received: from mirror.positive-internet.com [80.87.128.67] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ap7La-00038M-00; Fri, 06 Feb 2004 06:52:46 -0800 Received: by mirror.positive-internet.com (Postfix, from userid 1002) id 90B694354C; Fri, 6 Feb 2004 14:52:44 + (GMT) Date: Fri, 6 Feb 2004 14:52:44 + From: Thom May <[EMAIL PROTECTED]> To: Marc Cromme <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject:
Bug#231411: marked as done (Bug in modules.conf: order of modules)
Your message dated Fri, 6 Feb 2004 13:57:32 + with message-id <[EMAIL PROTECTED]> and subject line Bug#231411: Bug in modules.conf: order of modules has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 6 Feb 2004 12:29:49 + >From [EMAIL PROTECTED] Fri Feb 06 04:29:49 2004 Return-path: <[EMAIL PROTECTED]> Received: from mail.epost.de [193.28.100.151] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ap57F-0007cT-00; Fri, 06 Feb 2004 04:29:49 -0800 Received: from [80.138.168.131] (80.138.168.131) by mail.epost.de (6.7.015) (authenticated as [EMAIL PROTECTED]) id 4018DA2B00152971 for [EMAIL PROTECTED]; Fri, 6 Feb 2004 13:29:47 +0100 Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Message-Id: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed To: [EMAIL PROTECTED] From: Titus v. d. Malsburg <[EMAIL PROTECTED]> Subject: Bug in modules.conf: order of modules Date: Fri, 6 Feb 2004 13:29:42 +0100 X-Mailer: Apple Mail (2.612) Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_02_01 X-Spam-Level: Package: apache Version: 1.3.28-4 I have the default modules.conf. DirectoryIndex (index.html) is being ingored. Instead I get a directory listing generated by autoindex. The Problem seems to be the order in which the modules mod_dir and mod_autoindex are being added. The default modules.conf (in /etc/apache/) has ... LoadModule dir_module /usr/lib/apache/1.3/mod_dir.so LoadModule autoindex_module /usr/lib/apache/1.3/mod_autoindex.so ... It works if I simply switch these lines. I found the solution for this Problem at http://www.geocrawler.com/archives/3/192/2001/12/0/7411885/ Thanks for your dedication to this project, Titus v. d. Malsburg --- Received: (at 231411-done) by bugs.debian.org; 6 Feb 2004 13:57:35 + >From [EMAIL PROTECTED] Fri Feb 06 05:57:35 2004 Return-path: <[EMAIL PROTECTED]> Received: from parcelfarce.linux.theplanet.co.uk (www.linux.org.uk) [195.92.249.252] (93) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ap6UB-0001s1-00; Fri, 06 Feb 2004 05:57:35 -0800 Received: from willy by www.linux.org.uk with local (Exim 4.22) id 1Ap6U8-0003GO-FB; Fri, 06 Feb 2004 13:57:32 + Date: Fri, 6 Feb 2004 13:57:32 + From: Matthew Wilcox <[EMAIL PROTECTED]> To: "Titus v. d. Malsburg" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#231411: Bug in modules.conf: order of modules Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> User-Agent: Mutt/1.4.1i Sender: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_02_01 X-Spam-Level: On Fri, Feb 06, 2004 at 01:29:42PM +0100, Titus v. d. Malsburg wrote: > Package: apache > Version: 1.3.28-4 > > I have the default modules.conf. DirectoryIndex (index.html) is being > ingored. Instead I get a directory listing generated by autoindex. This problem was reported and fixed some time ago. Please upgrade to a more recent version of apache (sarge currently has 1.3.29.0.1-3 and sid has 1.3.29.0.1-5). I think this will fix your problem. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain
Bug#231423: apache2-doc: multi-language negociation not working - wrong filenames
Package: apache2-doc Version: 2.0.47-1 Severity: important Tags: patch After installing apache2-doc, the multi-language negociation does not work out of the box in the /var/www/apache2-default/manual directory and it's subdirectories. As far as I can see, it's the wrong filename which makes the problems: for example surfing into http://localhost/apache2-default/manual/index.html gives the output URI: index.html.de Content-Language: de Content-type: text/html; charset=ISO-8859-1 URI: index.html.en Content-Language: en Content-type: text/html; charset=ISO-8859-1 URI: index.html.ja.jis Content-Language: ja Content-type: text/html; charset=ISO-2022-JP URI: index.html.ko.euc-kr Content-Language: ko Content-type: text/html; charset=EUC-KR URI: index.html.ru.koi8-r Content-Language: ru Content-type: text/html; charset=KOI8-r However, renaming index.html to index.var and surfing into (the non-existent) http://localhost/apache2-default/manual/index.html gives the correct language-depending result. This change must be applied to all negociacion files, that is *.html --> *.var in all dirs. I suspect that similar applies to all *.xml files, but I do not know yet. Furthermore, The following wrong file permissions are found in this package: -rwxr-xr-x1 root root 277 Jul 5 2003 urlmapping.html -rwxr-xr-x1 root root18980 May 29 2003 urlmapping.html.en -rwxr-xr-x1 root root20544 May 29 2003 urlmapping.html.ja.jis please check also all these subdirs for the same errors. drwxr-xr-x2 root root 4096 Feb 6 12:44 developer drwxr-xr-x2 root root 4096 Feb 6 12:44 faq drwxr-xr-x2 root root 4096 Feb 6 12:44 howto drwxr-xr-x2 root root 4096 Feb 6 12:44 images drwxr-xr-x2 root root 4096 Feb 6 12:44 misc drwxr-xr-x2 root root12288 Feb 6 12:44 mod drwxr-xr-x2 root root 4096 Feb 6 12:44 platform drwxr-xr-x2 root root 4096 Feb 6 12:44 programs drwxr-xr-x2 root root 4096 Feb 6 12:44 search drwxr-xr-x2 root root 4096 Feb 6 12:44 ssl drwxr-xr-x 10 root root 4096 Feb 6 12:44 style drwxr-xr-x2 root root 4096 Feb 6 12:44 vhosts -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux cromme 2.4.24-1-386 #1 Tue Jan 6 19:18:04 EST 2004 i686 Locale: LANG=C, LC_CTYPE=C -- no debconf information
Bug#231411: Bug in modules.conf: order of modules
Package: apache Version: 1.3.28-4 I have the default modules.conf. DirectoryIndex (index.html) is being ingored. Instead I get a directory listing generated by autoindex. The Problem seems to be the order in which the modules mod_dir and mod_autoindex are being added. The default modules.conf (in /etc/apache/) has ... LoadModule dir_module /usr/lib/apache/1.3/mod_dir.so LoadModule autoindex_module /usr/lib/apache/1.3/mod_autoindex.so ... It works if I simply switch these lines. I found the solution for this Problem at http://www.geocrawler.com/archives/3/192/2001/12/0/7411885/ Thanks for your dedication to this project, Titus v. d. Malsburg
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > tags 231387 + pending Bug#231387: apache-perl isn't in sync with perl 5.8.3 There were no tags set. Tags added: pending > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#231387: apache-perl isn't in sync with perl 5.8.3
Package: apache-perl Version: 1.3.29.0.1-5 Severity: grave Justification: renders package unusable With perl 5.8.3 installed on the machine (from debian package), apache-perl does not contain the proper paths in the @INC path any longer to use with mod_perl programs. Basically all of the standard perl libs are in /usr/lib/perl/5.8.3 (or through it's symlink /usr/lib/perl/5.8). Same programs when run through standard CGI work fine as they use the perl interpreter under /usr/bin. Thanks, Steve -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.0-test11 Locale: LANG=C, LC_CTYPE=C Versions of packages apache-perl depends on: ii apache-common 1.3.29.0.1-5 Support files for all Apache webse ii debconf 1.4.8Debian configuration management sy ii dpkg1.10.18 Package maintenance system for Deb ii libapache-mod-perl 1.29.0.1-5 Integration of perl with the Apach ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.24.2.52-9 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.6-6 XML parsing C library - runtime li ii libmagic1 4.07-2 File type determination library us ii libpam0g0.76-15 Pluggable Authentication Modules l ii libperl5.8 5.8.3-1 Shared Perl library. ii mime-support3.24-1 MIME files 'mime.types' & 'mailcap -- debconf information: apache-perl/old-pidfile-set: * apache-perl/server-port: 80 * apache-perl/init: true * apache-perl/enable-suexec: false * apache-perl/document-root: /var/www * apache-perl/upgrade-from-apache-conflict: * apache-perl/server-name: patrick.frogshake.org * apache-perl/server-admin: [EMAIL PROTECTED]
Re: Tired of Overture and Google AdWords?
Hello: Tired of overpaying 20-30 cents per click at Overture and Google AdWords? If you are sick of it, then how does a rate of half a cent per click sound?? Try targeted visitors for only half a penny at the new pay-per-click search engine! http://www.surftheweb.com/freeclicks/ Yours, T O T U R N T O P.S. If you wish to get news about our PPC on a regular basis please ket us know! Otherwise you will not receive any more emails.
