Keith,

On Wed, July 7, 2010 14:14, Keith Williams wrote:
> Jan
>
> assume you meant dpkg

Typo, sorry. That's what somethimes happens when you try and do things at
a million miles an hour. Still, good perception and a solid understanding
often only needs half a word! :-)

> ii  apache2-mpm-prefork                   2.2.9-10+lenny8          Apache
> HTTP Server - traditional non-threade
> ii  apache2-utils                         2.2.9-10+lenny8          utility
> programs for webservers
> ii  apache2.2-common                      2.2.9-10+lenny8          Apache
> HTTP Server common files
> rc  libapache2-mod-php5                   5.2.6.dfsg.1-1+lenny8
> server-side,

Looks good! Last stuff I can add before it goes off into the total unknown
is:

To list full package contents, try (typed carefully this time):
dpkg -L package-name | less

If you can physically find all the files listed, then maybe by
reconfiguring the offending package could save you. You can do this with
the "dpkg-reconfigure" command.

Speaking for myself, I would backup any configs, and totally blat all the
above packages with "aptitude purge package1 package2 package3" et cetera,
and re-install from scratch afterwards. I simply don't have the time to go
into lenghty root-cause analysis exercises.


--
Regards,
Jan Henkins