last night my system ground to a halt with a full disk. looking at the logs, i discovered that they were the main if not the only resource hogs. (haven't looked for other sources of spurious disk usage). below is a sample of 'debug'. 'kern.log' and 'syslog' have the same messages. you can tell by the time stamps that something is going wild in my system.
Feb 7 10:50:26 localhost kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 31 Feb 7 10:50:26 localhost kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 31, Value: 0 Feb 7 10:50:26 localhost kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0 Feb 7 10:50:26 localhost kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 38 . . . Feb 7 10:53:01 localhost kernel: evbug.c: Event. Dev: usb-0000:00:1d.0-1/input0, Type: 2, Code: 0, Value: 1 Feb 7 10:53:01 localhost kernel: evbug.c: Event. Dev: usb-0000:00:1d.0-1/input0, Type: 0, Code: 0, Value: 0 Feb 7 10:53:01 localhost kernel: evbug.c: Event. Dev: usb-0000:00:1d.0-1/input0, Type: 2, Code: 1, Value: thanks in advance, tom arnall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
