Problem with preinst script - kills all apaches on machine with multiple apaches running side by side in different chroots but shared proc

Bug #65775 reported by Carthik Sharma
4
Affects Status Importance Assigned to Milestone
apache (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Originally reported using reportbug. Filing by proxy.

Original report follows:

From: SvenV <email address hidden>
To: Ubuntu Bug Tracking System <email address hidden>
Subject: Problem with preinst script, kills all apaches on machine with multiple apaches running side by side in different chroots but shared proc
Date: Wed, 06 Sep 2006 09:07:57 +0200
X-Mailer: reportbug 3.18ubuntu1

Package: apache
Severity: minor

-- System Information:
Debian Release: testing/unstable
  APT prefers dapper-updates
  APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-26-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
 1. the specific steps or actions you took that caused you to encounter the problem,
 2. the behavior you expected, and
 3. the behavior you actually encountered (in as much detail as possible).

Is this problem still occurring on the newest release of ubuntu? The package apache has been superseeded by apache2 and was not provided anymore since gutsy.

Thanks!

Changed in apache:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
Ralph Janke (txwikinger) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in apache:
assignee: txwikinger → nobody
importance: Undecided → Low
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.