Update on log filling up

2002-02-27 Thread Cary Jamison
Well, I was wrong. I thought I was getting tons of winCursorOffScreen () - hmm... messages in my log file, when actually the culprit is winShadowUpdateDDNL () - IDirectDrawSurface4_Blt () failed: 887601c2 The thing is my log was so big I could not tail or more it. I was using head and sa

RE: Log filling up

2002-02-27 Thread Cary Jamison
> From: Harold Hunt [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 27, 2002 12:17 PM > > > What is the purpose of this message (winCursorOffScreen () - > > hmm...)? It seems pretty useless. > > The message is mostly useless. The message was put there as sort of a > "heads up" in case

RE: Log filling up

2002-02-27 Thread Harold Hunt
never like seeing such things hard > coded in a program. Neither do I... but my priorities are fixed at the moment. Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Cary Jamison > Sent: Wednesday, February 27, 2002 11:11 AM >

Re: Log filling up

2002-02-27 Thread Alan Hourihane
You could always do rm /tmp/XWin.log ln -s /dev/null /tmp/XWin.log That should work and dump to /dev/null. Alan. On Wed, Feb 27, 2002 at 09:11:03 -0700, Cary Jamison wrote: > Modifying the code to put the log in /dev/null certainly doesn't seem like an >attractive solution. If I were to go t

RE: Log filling up

2002-02-27 Thread Cary Jamison
-Original Message- From: Alexander Gottwald [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 3:17 AM Cc: Cygwin/X list (E-mail) Subject: Re: Log filling up On Tue, 26 Feb 2002, Brian Genisio wrote: > You could always redirect the log file to /dev/null ... But this

RE: Log filling up

2002-02-27 Thread Cary Jamison
Modifying the code to put the log in /dev/null certainly doesn't seem like an attractive solution. If I were to go that far, I would rather just search for where the particular message is output that is causing the problem and disable it. Do others not have this problem? The only unique thing

Re: Log filling up

2002-02-27 Thread Alexander Gottwald
On Wed, 27 Feb 2002, Sylvain Petreolle wrote: > Why couldn't this be done by putting several > ">/dev/null" in startxwin ? Because you can't configure where the logfile is opened. The log is not written to stdout or stderr but to a file opened via fopen("/tmp/XWin.log") I have some test binarie

Re: Log filling up

2002-02-27 Thread Sylvain Petreolle
Why couldn't this be done by putting several ">/dev/null" in startxwin ? > But this can only be done by patching the binary. > Replace "/tmp/XWin.log" > "/dev/null\0log" (the \0 marks the character with > ascii code 0. > > bye > ago > -- > [EMAIL PROTECTED] > http://www.gotti.org

Re: Log filling up

2002-02-27 Thread Alexander Gottwald
On Tue, 26 Feb 2002, Brian Genisio wrote: > You could always redirect the log file to /dev/null ... But this can only be done by patching the binary. Replace "/tmp/XWin.log" "/dev/null\0log" (the \0 marks the character with ascii code 0. bye ago -- [EMAIL PROTECTED] http://www.gotti

Re: Log filling up

2002-02-26 Thread Brian Genisio
You could always redirect the log file to /dev/null ... --- Cary Jamison <[EMAIL PROTECTED]> wrote: > I have just installed Cygwin/X 4.2.0 from binaries and am enjoying accessing > both my Windows (XP Pro) and Linux boxes from one machine. However, I found > that I cannot leave X running too l

Log filling up

2002-02-26 Thread Cary Jamison
I have just installed Cygwin/X 4.2.0 from binaries and am enjoying accessing both my Windows (XP Pro) and Linux boxes from one machine. However, I found that I cannot leave X running too long or my log fills up with the following message: winCursorOffScreen () - hmm... This can fill up a coup