[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tlf-devel] Cwdaemon 0.8 beta on Slackware 9.1

From: Rein Couperus
Subject: Re: [Tlf-devel] Cwdaemon 0.8 beta on Slackware 9.1
Date: Thu, 22 Apr 2004 14:58:50 +0200
User-agent: KMail/1.5.4

I have found the cause of the 'missing character syndrome', in fact I am now 
able to reproduce it whenever I want.

When I send a 'message abort' to cwdaemon DURING a message, the message is 
When I send a 'message abort' to cwdaemon AFTER or BEFORE a message, the first 
character of the following message is not sent!! It is displayed o.k. in the 
debug routine but it is not sent. That is also the reason why Wolf did not 
find it :)
You can simply reproduce the fault by typing  ESC  in tlf and then sending any 
message... and watch cwdaemon swallowing the first character of your call...

I have stopped famd (why is that running anyway) and I have no bit errors any 
more. Even at 40 wpm. Strangely enough, the CPU load monitor as well as the 
memory map have not changed (still 94% idle in top and memory load 80% (no 

Tnx, this is a relief.... cwdaemon 0.8 is now as crisp as the mfj1278...

Rein Pa0R

On Thursday 22 April 2004 11:31, Joop Stakenborg wrote:
> > Sure....
> > I think apmd and acpid are not running.
> >
> >    11 ?        SW    16:34 [kjournald]
> >   330 ?        S     18:17 /usr/sbin/famd -T 0
> > 14085 pts/1    S      6:38 cwdaemon -n
> [ deleted some data from the output ]
> > The 'missing character' feature happens sporadically, only when the
> > system has
> > been idle for some seconds (when you are calling the dx station in a pile
> > up,
> > "A0R"), and never in the middle of a message.
> Interesting observation Rein. Looking at the output there are 2 processes
> standing out clearly that eat CPU: famd and kjournald. One reason for the
> missing characters could be that some other process is eating resources,
> so cwdaemon never gets a chance to send characters properly.
> There are 2 tests that you can do:
> - log out of KDE, start up a console (Ctrl-Alt-F1) and kill famd (this is
> the file alteration monitor, used by KDE). Next start tlf to see if that
> helps.
> - Copy your xfs filesystem (I guess that's what your using) to an ext2
> partition and boot from that partition. This way we never use kjournald.
> Then test cwdaemon on this partition.

address@hidden or address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]