I guess I'm alittle confused... I don't see any errors related to NULL file handles. And the thing about the ServerRoot starting with a /, it seems that the process found the config file okay, so wouldn't it also know what the ServerRoot should be?
And why doesn't Apache complain about the invalid ServerRoot variable when started from the command line? Even with the -t option, the error is unrecognized. I tried adding the -d option through the Service Manager to use when starting the service manually, with no change in behavior. I'll keep looking... Tks, Dwayne William A. Rowe, Jr. wrote: >From: "Dwayne Miller" <[EMAIL PROTECTED]> >Sent: Monday, February 04, 2002 5:13 PM > > >>>Which Win32 OS are you using, exactly? >>> >>I'm on Windows 2000, build 2195, SP2 >> > >Win2000/XP have NULL stdin/stdout/stderr handles... > >the create_process() invokes ap_open_stderr_log() which in turn invokes >apr_file_open_stderr() attempting to open a NULL STDERR handle. > >The patch I just committed reinvokes ap_open_stderr_log() after we jump into >the service control manager track with a stderr pipe that we capture to the >application event log. > >The right solution is to finish the move of the service manager code in the >apr_app_initialize code (apr_initialize + apr_app_main) which I hadn't finished >yet, and didn't plan to for a week, maybe two =-/ > >>I was looking at mpm_winnt.c, where the apr_filepath_merge() call is >>made. It looks like it is trying to build the -d argument to use when >>starting the service, but it's obviously not having the desired effect. >> > >That's where things are still goofy... I'm still debugging. > >More updates as they become available. > >Bill >
