>Number: 5156 >Category: os-windows >Synopsis: apache not running correctly from command line >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: duplicate >Submitter-Id: apache >Arrival-Date: Fri Oct 15 15:10:02 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: NT 4.0,pre-compiled >Description: same error as 3767. I also tried a few other test cases. used -d flag:
apache -d C:\lkjsadf got an error for directory C:/lakgh...: notice how the slashes were switched. This also happens with the -f flag. It would appear that somewhere all of the input arguments are being parsed and that all '\' are being replaced by '/'. For obvious reasons this isn't so good under windows. A co-worker told they didn't see this problem when using 1.3.9 but I haven't even checked to see if that release exists and is stable. >How-To-Repeat: see PR 3767 >Fix: Remove all command line parsing that translates '\' to '/'. ez n'uf >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 make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]