Bug#240772: apache2-common: files in apache2-default should be in /var/www
Package: apache2-common Version: 2.0.48-8 Severity: normal When installing an apache2 mpm, the default document root is /var/www. This is correct, but apache2-common doesn't put anything into /var/www, other than the apache2-default subdirectory. People who then use apache see a directory list, and get the if you see this, the installation of apache was successful page if they go into the apache2-default subdirectory. Apache2-common should put at least an index.html into /var/www. Obviously, you'll need to figure out how to get apache-common and apache2-common to co-exist happily, with both wanting to put files into /var/www. Another alternative (and preferred, imo) is to split apache2-common and apache-common out further; right now they contain both arch specific binaries and arch-independant files. Why not make an apache-files (or apache-data) package that contains the various icons (I'm not sure how different /usr/share/apache2/icons is from the apache1 icons) and /var/www files, and have the apache-common and apache2-common packages contain binaries and apache-version-specific scripts? Both apache-common and apache2-common could depend upon apache-files. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.4-1-686 Locale: LANG=C, LC_CTYPE=C Versions of packages apache2-common depends on: ii debconf 1.4.18 Debian configuration management sy ii debianutils 2.8 Miscellaneous utilities specific t ii libapr0 2.0.48-8 The Apache Portable Runtime ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.24.2.52-16Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.6-8 XML parsing C library - runtime li ii libldap22.1.26-1 OpenLDAP libraries ii libmagic1 4.07-2 File type determination library us ii libssl0.9.7 0.9.7d-1 SSL shared libraries ii mime-support3.26-1 MIME files 'mime.types' 'mailcap ii net-tools 1.60-9 The NET-3 networking toolkit ii openssl 0.9.7d-1 Secure Socket Layer (SSL) binary a ii ssl-cert1.0-7Simple debconf wrapper for openssl ii zlib1g 1:1.2.1-5compression library - runtime -- no debconf information
Processed: your mail
Processing commands for [EMAIL PROTECTED]: tags 240301 pending Bug#240301: apache2 has broken init script There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Место проведения презентации
Title: Untitled Document I 6 : : . , . 1/3, - . : , , ,, . : 1. 1.1. 1.2. 1.3. - ; - ; - ; - . 2. 2.1. 2.2. - ; -; - . 2.3. 3. 3.1 - ; - ; -. 3.2. 3.3. - - ; - . 4. 4.1. 4.2. 4.3. 4.4. 5. : - - , , - - , . : : 500 . : , , , - , , , . : 2 5%. 3 7%. . . : . / (044) 2.28.9 , 4.5.4 9.8 7.9 DotMail. 303267184.
remove me!!!!!!!!!!
Get me off your list or otherwise, I will file a complaint with Federal Trade Commission. Paul Stefanski
Bug#240961: apache segfaults on start
Package: apache
Version: 1.3.29.0.2-4
Severity: normal
Upon starting apache, both the init script and apachectl will report
successfully starting the server. However, none have started. If I
strace -f apachectl start, it turns out that the server is segfaulting.
stat64(/dev/urandom, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9),
...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 11374 detached
There was a bug where someone else encountered a SEGV (#230539) caused
by recursively including the config files. I purged all of my config
files and clean installed the package, and the problem persists.
I have had this problem occur for the past few months, and it has
happened on 2.4.21-xfs and 2.4.23-xfs.
Thanks,
David
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.23-xfs
Locale: LANG=C, LC_CTYPE=C
Versions of packages apache depends on:
ii apache-common 1.3.29.0.2-4 Support files for all Apache webse
ii debconf 1.4.16 Debian configuration management sy
ii dpkg1.10.20 Package maintenance system for Deb
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libdb4.24.2.52-16Berkeley v4.2 Database Libraries [
ii libexpat1 1.95.6-8 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 logrotate 3.6.5-2 Log rotation utility
ii mime-support3.26-1 MIME files 'mime.types' 'mailcap
ii perl5.8.3-2 Larry Wall's Practical Extraction
-- debconf information:
* apache/enable-suexec: false
* apache/server-name: nx01.coolhack.net
* apache/document-root: /var/www
* apache/server-port: 80
* apache/init: true
* apache/server-admin: [EMAIL PROTECTED]
Re: Bug#240961: apache segfaults on start
Hi David,
On Mon, 29 Mar 2004, David Stipp wrote:
stat64(/dev/urandom, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9),
...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 11374 detached
There was a bug where someone else encountered a SEGV (#230539) caused
by recursively including the config files. I purged all of my config
files and clean installed the package, and the problem persists.
Not only. Which modules are you loading? (usual bunch of questions) did
you try to disable php4? did you try to disable mod_perl?
I have had this problem occur for the past few months, and it has
happened on 2.4.21-xfs and 2.4.23-xfs.
I don't think it's a kernel problem.. or i hope not at least.
Please let me know
Fabio
--
user fajita: step one
fajita Whatever the problem, step one is always to look in the error log.
user fajita: step two
fajita When in danger or in doubt, step two is to scream and shout.
Re: Bug#240961: apache segfaults on start
On Tue, Mar 30, 2004 at 07:08:47AM +0200, Fabio Massimo Di Nitto wrote:
On Mon, 29 Mar 2004, David Stipp wrote:
stat64(/dev/urandom, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9),
...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 11374 detached
There was a bug where someone else encountered a SEGV (#230539) caused
by recursively including the config files. I purged all of my config
files and clean installed the package, and the problem persists.
Not only. Which modules are you loading? (usual bunch of questions) did
you try to disable php4? did you try to disable mod_perl?
Well, I seem to have traced down this problem here. When apache started
working once I disabled php4, I started to twiddle with the php4 modules
that were being loaded. I traced down the problem to the php4-imap
module.
Looks like this ticket should get bounced over that way.
Thanks for your fast response.
David
