![]() |
2010-12-02
, 13:40
|
Posts: 992 |
Thanked: 738 times |
Joined on Jun 2010
@ Low Earth Orbit
|
#2
|
echo "" > /tmp/Xorg.0.log
![]() |
2010-12-02
, 14:46
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#4
|
![]() |
2010-12-02
, 14:59
|
Posts: 670 |
Thanked: 747 times |
Joined on Aug 2009
@ Kansas City, Missouri, USA
|
#5
|
![]() |
2010-12-02
, 16:17
|
Posts: 63 |
Thanked: 26 times |
Joined on Jul 2010
@ Canada
|
#6
|
Or rm -rf /tmp/* and umount /tmp, that way /tmp will share space with /
(II) button (value): 0(0) (II) EV_KEY (code, value, ignored, ev.code, val, flags): 0, 0, 0, 28, 0, 33
![]() |
2010-12-02
, 16:31
|
Posts: 228 |
Thanked: 145 times |
Joined on Dec 2009
|
#7
|
![]() |
2010-12-02
, 16:40
|
|
Posts: 288 |
Thanked: 175 times |
Joined on Oct 2010
@ Petaling Jaya, Selangor, Malaysia
|
#8
|
![]() |
2010-12-02
, 16:44
|
Posts: 24 |
Thanked: 5 times |
Joined on Oct 2010
@ Portugal
|
#9
|
That doesn't work as the log file handle is still open and kept by the X server. You will see that the file is gone, but the disk space won't be available again.
The echo > Xorg.0.log trick seems to work (at least "df" is happy about it)
Now am I the only one seeing these lines in their Xorg log?
Code:(II) button (value): 0(0) (II) EV_KEY (code, value, ignored, ev.code, val, flags): 0, 0, 0, 28, 0, 33
![]() |
2010-12-02
, 17:44
|
Posts: 63 |
Thanked: 26 times |
Joined on Jul 2010
@ Canada
|
#10
|
Just a completely wild guess, but could it be a keyboard hardware problem?
My logic is: if EV_KEY is a keyboard event, then maybe the system is being overrun by spurious events generated by a hardware problem...
I have a problem that shows from time to time: m Xorg log brows very 'large' and fills the poor 1MB /tmp partition. When that happens, the device doesn't fumction very well, for obvious reasons...
I've copied the beginning of my xorg log file. The last 2 lines repeat themselves ad nauseam until no more space is available. I'm running PR 1.3 (in case that helps)
Any idea?
Thanks!
Last edited by jprobichaud; 2010-12-03 at 17:38. Reason: updating the title