On Tuesday 20 October 2009 21:45:35 David Baron wrote:
> >Last couple of days! Filled up /var causing numerous problems.
> >
> >These files are over 1 gig. I deleted the day-old ones to free up space.
> >
> >The older ones are tiny.
> >
> >What's happening? Fix?
>
> These are mostly messages from gpm
> Oct 20 14:23:47 d_baron /usr/sbin/gpm[4547]: *** err
> [daemon/getmousedata.c(47)]:
> Oct 20 14:23:47 d_baron /usr/sbin/gpm[4547]: Error in read()ing first: No
> such device
>
> This is a microsoft wireless usb mouse. Sometimes, the receiver needs be
> reset but this is occasional. Gpm was not upgraded recently?
>
> How might one surpress these log entries? They are of little value.
>

This has happened a few more times.
When it occurs, it cripples the system since anything that touches any file on
/var, logs, pid files, etc., fails. Xorg is frozen, cannot be reset.

Funny, I can get on from the outside using ssh (should not this be logged!?!)
and fix it, reboot, etc.

Is this a gpm bug? An Xorg bug (since this is polling the mouse)?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tuesday 20 October 2009 21:45:35 David Baron wrote:
> >Last couple of days! Filled up /var causing numerous problems.
> >
> >These files are over 1 gig. I deleted the day-old ones to free up space.
> >
> >The older ones are tiny.
> >
> >What's happening? Fix?
>
> These are mostly messages from gpm
> Oct 20 14:23:47 d_baron /usr/sbin/gpm[4547]: *** err
> [daemon/getmousedata.c(47)]:
> Oct 20 14:23:47 d_baron /usr/sbin/gpm[4547]: Error in read()ing first: No
> such device
>
> This is a microsoft wireless usb mouse. Sometimes, the receiver needs be
> reset but this is occasional. Gpm was not upgraded recently?
>
> How might one surpress these log entries? They are of little value.
>
BTW, One program I know will consistently produce these errors: The otherwise
quite lovely krossword puzzle program for kde4. Could find no clues scanning
the code but it smells of some recursion problem handling mouse messages.


Possible workaround:

A cron to check the size of these files, mv or rm them if they get beyond a
certain size. This would at least protect the system operation.

How do I do it?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org