From owner-freebsd-x11@FreeBSD.ORG  Tue Feb 10 04:43:34 2009
Return-Path: <owner-freebsd-x11@FreeBSD.ORG>
Delivered-To: freebsd-x11@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3C14A106566C
	for <freebsd-x11@freebsd.org>; Tue, 10 Feb 2009 04:43:34 +0000 (UTC)
	(envelope-from ulrich@pukruppa.net)
Received: from pukruppa.net (pukruppa.net [213.146.114.24])
	by mx1.freebsd.org (Postfix) with ESMTP id AD54B8FC17
	for <freebsd-x11@freebsd.org>; Tue, 10 Feb 2009 04:43:33 +0000 (UTC)
	(envelope-from ulrich@pukruppa.net)
Received: from pukruppa.net (localhost [127.0.0.1])
	by pukruppa.net (8.14.3/8.14.3) with ESMTP id n1A4l2nJ045693
	for <freebsd-x11@freebsd.org>; Tue, 10 Feb 2009 05:47:03 +0100 (CET)
	(envelope-from ulrich@pukruppa.net)
Message-ID: <499106C6.7040702@pukruppa.net>
Date: Tue, 10 Feb 2009 05:47:02 +0100
From: Peter Ulrich Kruppa <ulrich@pukruppa.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090130)
MIME-Version: 1.0
To: freebsd-x11@freebsd.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Gigantic gdm-2.24 log files
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
	<mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
	<mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2009 04:43:34 -0000

Hi,

I posted this messages to freebsd-gnome@freebsd.org yesterday and 
Joe Marcus Clarke answered:

 > Looks like an X issue to me.
 >
 > Joe

so I try again here!

I run xorg-7.4 and when I list /var/log/gdm I get some extremly 
big files:
     ------------------------------------
ls -lh
total 11349526
[...]
-rw-r--r--  1 root  gdm   1,4K  7 Feb 07:15 :0-slave.log.4
-rw-r--r--  1 root  gdm   4,7G  9 Feb 16:24 :0.log
               		  ^^^^
-rw-r--r--  1 root  gdm   102K  8 Feb 19:02 :0.log.1
-rw-r--r--  1 root  gdm   6,1G  8 Feb 18:06 :0.log.2
               		  ^^^^
-rw-r--r--  1 root  gdm   8,1M  7 Feb 07:31 :0.log.3
-rw-r--r--  1 root  gdm   2,5M  7 Feb 07:19 :0.log.4
[...]
     ------------------------------------

The remaining files behave normally. What might have happened there?

This is a
	# tail -f :0.log
     ---------------------------------
[...]
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
(==) VESA(0): Write-combining range (0x0,0x1000) was already clear
^C
     -------------------------------------

Perhaps these messages can simply be turned off?


Greetings,

Uli.