Re: Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread William A. Rowe, Jr.
At 02:41 PM 4/4/2003, Bill Stoddard wrote: >>Unless you are doing pphrase tricks, you shouldn't create the Apache >>service to 'interact with desktop'. By default Apache installs itself >>non-interactive. >>If it can still interact, you have some really weird permissions mojo >>going on in that b

Re: Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread Spinka, Kristofer
In addition, I was just thinking that there might be a missing "| CREATE_NO_WINDOW" on the creation flags for CreateProcess. /kristofer On Fri, 4 Apr 2003, William A. Rowe, Jr. wrote: > At 01:29 PM 4/4/2003, Spinka, Kristofer wrote: > > Are you running Apache as a service? If so, and you a

Re: Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread Bill Stoddard
William A. Rowe, Jr. wrote: At 01:29 PM 4/4/2003, Spinka, Kristofer wrote: Are you running Apache as a service? If so, and you are still having this problem, we have to do some CreateProcess tricks to keep the console window from being visible on the current Window Station. Unless you are doing

Re: Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread William A. Rowe, Jr.
At 01:29 PM 4/4/2003, Spinka, Kristofer wrote: > Are you running Apache as a service? If so, and you are still having >this problem, we have to do some CreateProcess tricks to keep the console >window from being visible on the current Window Station. Unless you are doing pphrase tricks, you shou

Re: Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread Spinka, Kristofer
Are you running Apache as a service? If so, and you are still having this problem, we have to do some CreateProcess tricks to keep the console window from being visible on the current Window Station. /kristofer On Fri, 4 Apr 2003, Bill Stoddard wrote: > Andre Schild wrote: > > Hello, > > >

Re: Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread Bill Stoddard
Andre Schild wrote: Hello, we have seen this behaviour with 2.0.45 when it can't write to the logfile (for whatever reason) Our server under NT 4.0 logs just fine (with ~20 rotatelogs running for the different vhosts.) André Interesting that I've never seen this problem before. I am still seeing

Antw: win32 piped logs really broken in 2.0.45

2003-04-04 Thread Andre Schild
Hello, we have seen this behaviour with 2.0.45 when it can't write to the logfile (for whatever reason) Our server under NT 4.0 logs just fine (with ~20 rotatelogs running for the different vhosts.) André >>> [EMAIL PROTECTED] 04.04.2003 19:04:01 >>> See subject... Setup customlog to do piped a