This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Log filling up
- From: Alan Hourihane <alanh at fairlite dot demon dot co dot uk>
- To: Cary Jamison <Cary dot Jamison at powerquest dot com>
- Cc: "Cygwin/X list (E-mail)" <cygwin-xfree at cygwin dot com>
- Date: Wed, 27 Feb 2002 16:22:47 +0000
- Subject: Re: Log filling up
- References: <DBB106D1C9FDAC408B360E2D0A5673823FB9DC@pqorex02.powerquest.pq>
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 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 about my setup is that I use Andrei Gourianov's goScreen as a virtual desktop manager under windows. I haven't tested to see if this affects the XWin.log or not. I can't imagine that it would, since the log fills up even when my desktop is set to the one where X is running, so it shouldn't see any difference.
>
> What is the purpose of this message (winCursorOffScreen () - hmm...)? It seems pretty useless.
>
> It would seem like a good idea to be able to configure where the log file goes, though. I never like seeing such things hard coded in a program.
>
> Cary
>
> ---
> Cary Jamison
> Cary.Jamison@PowerQuest.com
> (801) 705-8685 voice
> (801) 705-4685 fax