[vdr] Re: Problem with master timer in 1.2.4pre

[Matthias Schniedermeyer <ms@citd.de>]

On Wed, Aug 27, 2003 at 11:43:35AM +0200, Robert Bartl wrote:
> i traced it with ethereal and master-timer really didnt send quit. (after
> lste)
> perhaps i configured something wrong or changed some code, to trigger that
> case..

"quit" is send when a programm (that made a connection) exists.
The close in in an END{} block. This works for this cases:
a) Normal exit
b) die ();
c) kill/CTRL-C

with one exception, if an "unfinished" ("/r/n" missing") command is on
the queue to VDR then it doesn't work.

e.g.
lste (without \r\n) is send, and then the program dies, then "quit\r\n"
is send and VDR sees "lstequit\r\n" which is garbage for VDR.

To test this you could prepend the quit with "\r\n". This should make
sure that this quit gets through.

> but imo shouldnt that be a problem and vdr shouldnt hang claiming all cpu..
> (and detect a closed connection).

Good point. ;-)




Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.