On Tuesday 20 Aug 2013 16:10:59 Peter Humphrey wrote: > Hi List, > > The other day my LAN server had an upgrade to PHP, from 5.4.17 to 5.5. Next > time apache restarted, it couldn't because it was looking for > /usr/lib/apache2/modules/libphp.5.so. The library seemed to be in place, > but in fact it was a broken symlink to > /usr/lib/php5.4/apache2/libphp.5.so. > > Running revdep-rebuild failed to find the problem (though it did find a > problem with cairo, so I didn't mind the time spent). I had to remerge PHP > myself to fix it. > > Just a little cautionary tale.
I had the same symptom. Just as I was about to manually remove the old and create my own new symlinks, I remembered that these days eselect looks after such things. So I used eselect to declare php-cli, apache2 and some such links. Restarted apache and all worked fine. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
