I am, for the moment, OK with the fact that if I close Mplayer by hitting the 'Q' key things are fine but hitting the close button on the corner of the Mplayer video window results in things not being closed out properly further resulting in not being able to use or unload the IVTV driver until I reboot.
There is a secondary element to this. I don't always remember to hit the 'Q' key and so a continuous stream of: ivtv: ENC IRQ OVERFLOW: #1107 Stealing a Buffer, 1024 currently allocated messages are generated and if the machine is left running long enough eventually filling up the partition where the log files are kept. In my case as I expect it is with most people, this is my root partition and so upon filling up the partition extraordinary measures are needed to clear out the log files to free up the space to allow a normal boot to be successful. This poses the question. Is it possible to design things so under normal logging levels the sparse message condition is handled with individual messages logged as is the current case and the many messages condition is recognized by a routine that says 'Hey there are too many of these messages being generated and I am going to stop logging them until some sanity returns'? Later, Seeker ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
