>Number: 3793 >Category: general >Synopsis: Incessantly changing paths >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Fri Jan 29 06:30:00 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.4 >Environment: IRIX monster 6.5 05190003 IP22 MIPS Pro C (cc) >Description: While this is not a bug, per se, I think it is still woth mentioning. We upgraded our old Apache 1.2 server to 1.3.2 several months ago. It was a big problem for us that the default paths had changed. These paths, of course can be changed in the configuration files, but we wanted to try to keep up with the changes. After some messing around, we finally got all of the paths changed. Life was happy. I upgraded to 1.3.3 when it was release. More happiness. I saw that 1.3.4 was released and I was eccstatic! Little did I know that the default paths had changed AGAIN! Now, in order to stay with the default paths, I must go through and change all sorts of paths in various CGI's, log analyzers, etc. >How-To-Repeat: Upgrade from Apache 1.2 to 1.3.3 then to 1.3.4 >Fix: The old paths or the new, I don't care, but the constant changing is really an issue for some of us anal-retentive administrators who don't want to stray from the norm. Ad my dear grandfather says "S**t or get off the pot" meaning, pick one or pick the other, just pick! >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
