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
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
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
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
-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 can only
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
Cary,
> 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 someone every reported seeing the message... then we
would know that we need to implement the functi
> 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
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
Great job including the XTrap extension in the xcygwin binary release.
You are missing libXETrap.a - the XTrap client side library with which
you must have statically linked the XTrap sample clients?
Building the XTrap library requires some Xt internal header files hence
it would be a heck of a l
[Remail to Cygwin/XFree86 list of private email I sent with libXTrap.a
attached.]
Are you referring to the file that I have attached?
In XFree86's CVS tree, there is a directory called xc/lib/XTrap with most
file names starting with XE*, such as XETrapInit.c. This directory is being
built and X
The library has been provided by Harold Hunt who reports that this is a
packaging problem.
--Robert
12 matches
Mail list logo