Hello Martin,I meant it otherwise. If /usr/local/bin/pca is a link to /var/apache2/cgi-bin/pca-proxy.cgi I could avoid this followsymlinks in the httpd config.
I will try it myself after arriving of the next release of pca. Thanks again, thomas Martin Paul wrote:
Hi,Sorry, but I did not realize that this was a problem.Not your fault - the current behaviour really isn't what you would expect. I think I'll soon break backwards compatibility and make pca-proxy only read pca-proxy.conf in the future.BTW.: Is it ok to set a softlink from /usr/local/bin/pca to .../cgi-bin/pca-proxy.cgi to get the cgi updated simply with pca --update now ? Until now I had to copy it manually from /usr/local/bin to the cgi-bin directory after each update.Yes, that should be fine. Make sure that your web server follows symlinks, this might not be the default (in apache's configuration, look for "FollowSymLinks").One day I'll add auto-update for the proxy as well. It's not that urgent, though - I rarely change code in the proxy mode section of pca, so it isn't that important to have the most recent release there.Martin.
-- Dr. Thomas Bleek, Netzwerkadministrator GeoForschungsZentrum Potsdam Telegrafenberg G261 D-14473 Potsdam Tel.: +49 331 288- 1818/1681 Fax.: 1730 Mobil: +49 172 1543233 E-Mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
