7 Jul
2010
7 Jul
'10
2:14 p.m.
Jan,
Just saw second half of this reply after sending my last one.
Will give it a try.
Thanks for your help (and thanks to all others) I feel guilty taking up
everyone's time.
I'll give it a try
Keith
On 7 July 2010 14:55, Jan Henkins <jan(a)henkins.za.net> wrote:
Keith,
On Wed, July 7, 2010 14:14, Keith Williams wrote:
--
Keith Williams
www.jogle2010.org.uk
www.westnorfolkrspca.org.uk
I'm sick of following my dreams. I'm just going to ask them where they're
going and hook up with them later.
- Mitch Hedberg
Outside of a dog, a book is man's best friend. Inside of a dog it's too dark
to read.
- Groucho Marx
The most dangerous strategy is to jump a chasm in two leaps.
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