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