>Number: 2281 >Category: general >Synopsis: Setting ScriptAlias confounds lock_fname resulting in server >that wont start >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon May 25 14:40:00 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3b6 >Environment: SunOS XXXXXX.chpc.utah.edu 5.5.1 Generic_103640-19 sun4u sparc SUNW,Ultra-2 Using Sun SPRO C compiler. >Description: With 1.3b6 built with:
--enable-module=status \ --enable-module=info \ --enable-module=proxy \ --enable-module=rewrite \ --enable-module=auth_anon \ --enable-module=auth_dbm \ --enable-module=digest \ --enable-module=expires \ --enable-module=mime_magic \ --enable-module=speling \ --enable-module=usertrack \ --enable-module=so \ if I set ScriptAlias (to an existing directory) and start the server with the apachectl script, the server starts up and then exits seemingly before being done reading all its config files. The error log reports: open: No such file or directory Cannot open lock file: The only code I can find that ever outputs this message is in src/main/http_main.c and it also outputs ap_lock_fname (in the second line), which as seen above is empty. I haven't traced down exactly what it's set to (ie. null, empty string, or spaces-only). At first I thought the problem was my introduction of suexec into the configure options. I finally realized that uncommenting the setting of ScriptAlias caused it. When I comment it back out again the server runs. This seems serious if anybody else can reproduce this problem since it makes the server un-runnable. >How-To-Repeat: Has anybody seen this problem already? I'd think it's either easily reproduced using the same C compiler and OS by commenting in & out the ScriptAlias directive or else it's something completely screwy that I've goofed on. >Fix: The interaction between setting ScriptAlias and lock_fname appears impossible since I can't find any code that deliberately links the two. I'd guess the problem's either in memory management then or something that I'm doing that's completely screwy. >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. ]