|
From: Leif M. <le...@ta...> - 2006-02-10 14:35:58
|
Daniel,
It is possible to explicitly flush stdout by calling
fflush(stdout). I added a new
wrapper.console.flush=true property, which when set to true will do this
after
each line of output logged to the console. Could you try out the
snapshot below
with and without the above property and let me know if it makes any
difference.
When using the wrapper in normal operation, it doesn't seem to do
anything at
all. The performance tests are unaffected one way or the other. That
may be
because the command prompt is causing an automatic flush or something.
http://wrapper.tanukisoftware.org/tmp/3.1.2-d/wrapper-windows-x86-32-3.2.0-e.zip
Cheers,
Leif
Daniel Mace wrote:
> Leif,
>
>
>> Strange. I assume you are using the console output of the Wrapper.
>> That output should
>> be getting sent to stdout in pretty much real time. It shows
>> up in the console immediately
>> on all platforms at least. I wonder if there is some kind
>> of a flush
>> that needs to be done
>> that is not needed the way the wrapper is normally used. You
>> might want to try poking
>> around in the logger.c file to see if you have any ideas.
>> The Windows
>> version makes
>> use of the WriteConsole function to write to the console if
>> running as a service and a console is being displayed. Other
>> cases simply write to stdout.
>>
>
> I will take a peek at it today to see if I notice anything obvious...
>
>
>> I'll poke around, but other than flushing ??? Not sure what
>> it would be. Let me know how your program is running. If
>> you are running as a service, then you may need to set the
>> wrapper.ntservice.console property to get a console to capture from.
>>
>
> I apologize! I should have mentioned in my first message: I am running
> in console mode, NOT as a service. Hopefully this will be a clue.
>
> Thanks for the tips. The search continues...
>
> Daniel Mace
> Software Engineer, Payroll Integration
> benefitfocus.com
> 843-849-7476 x393
>
|