Hi all,
I could use some advice on how to handle the following situation.
I adopted a web application package that used to set a symlink under
/var/www: /var/www/phpmyadmin - /usr/share/phpmyadmin. This was not good:
we shouldn't touch /var/www and not enable phpmyadmin without asking. So
now I
On Tue, 24 Apr 2007 11:38:04 +0200, Thijs Kinkhorst wrote:
My question is how to deal with this legacy symlink. I can just rm it on
upgrade, but the admin might have put a different symlink there, or
depends on the symlink to keep phpmyadmin configured.
Remove it on upgrade if it still points
Am Dienstag, den 24.04.2007, 11:38 +0200 schrieb Thijs Kinkhorst:
I could use some advice on how to handle the following situation.
I adopted a web application package that used to set a symlink under
/var/www: /var/www/phpmyadmin - /usr/share/phpmyadmin. This was not good:
we shouldn't
On Tue, 24 Apr 2007 13:10:59 +0200, Daniel Leidert wrote:
I adopted a web application package that used to set a symlink under
/var/www: /var/www/phpmyadmin - /usr/share/phpmyadmin. This was not good:
we shouldn't touch /var/www and not enable phpmyadmin without asking.
Why? What is so bad
On Tue, April 24, 2007 13:10, Daniel Leidert wrote:
we shouldn't touch /var/www and not enable phpmyadmin without asking.
Why? What is so bad with this symlink?
- It touches /var/www which is under the administrator's control;
- It does not make sense, since the document root might be
On Tue, Apr 24, 2007 at 10:10:29AM +, Sam Morris wrote:
On Tue, 24 Apr 2007 11:38:04 +0200, Thijs Kinkhorst wrote:
My question is how to deal with this legacy symlink. I can just rm it on
upgrade, but the admin might have put a different symlink there, or
depends on the symlink to keep
On Tue, 24 Apr 2007, Sam Morris wrote:
On Tue, 24 Apr 2007 11:38:04 +0200, Thijs Kinkhorst wrote:
My question is how to deal with this legacy symlink. I can just rm it on
upgrade, but the admin might have put a different symlink there, or
depends on the symlink to keep phpmyadmin
7 matches
Mail list logo
