7 Jul
2010
7 Jul
'10
2:24 p.m.
Hello,
On Wed, Jul 07, 2010 at 02:55:51PM +0100, Jan Henkins wrote:
On Wed, July 7, 2010 14:14, Keith Williams wrote:
I suspect that what has happened is that Keith has deleted
/etc/init.d/apache2 manually. Reinstalling the package which owns
this file (apache2.2-common) will not replace this file since Debian
assumes that if the admin deleted it manually then they really don't
want it there.
So, what I would do is reinstall this file from backups. Backing up
/etc is probably something that everyone should do on every machine,
since it's small and has lots of important stuff.
BitFolk offers a free backup service:
http://bitfolk.com/customer_information.html#toc_2_Local_backups
Assuming that Keith hasn't got backups..
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.
I am not sure if this will work, but I'd certainly try it.
Failing that I'd probably purge apache2.2-common and install it
again.
If you purge a package instead of removing it, then all traces of
its config files will be removed, so it will be possible to install
it again and get fresh copies.
The downside is that this is going to remove every file in
apache2.2-common even if you've edited them. The upside is that if
you've deleted more than just /etc/init.d/apache2 then you will get
the other files back too.
You can see which files are going to be removed by listing the files
in the apache2.2-common package:
$ dpkg -L apache2.2-common
You can restrict that to just config files (which are the only ones
you're likely to have edited) like this:
$ dpkg-query -W -f='${Conffiles}\n' apache2.2-common
And you can use the checksums on the end of each line to tell which
files have actually been modified:
$ dpkg-query -W -f='${Conffiles}\n' apache2.2-common | awk 'OFS="
" {print $2,$1}' | md5sum -c 2>/dev/null | grep FAILED
Any file showing up there as FAILED has been modified since the
package was installed, and will be removed when the package is
purged, so you might want to take a backup of them.
To actually purge the package:
# apt-get purge apache2.2-common
Then reinstall it again.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting