On Mon, 30 Oct 2006, dwelch91 wrote: > Yes, you are correct. It was partly your input into these issues that moved > me to change it to how it is done today.
Yeah. And it made it much easier to one day port hplip to be network-aware (as in hp-toolbox in one box, hpssd/hpiod in another), which people running printer server farms would really appreciate. BTW: Unless there is a very good reason for hpiod select() calls to timeout, please make they don't timeout easily. They will get interrupted by signals anyway, and it just wastes resources waking up hpiod when there is no data to be processed. The fact that it also fills up our strace debug screens is just aggravating, too :-) > I think I/we can get the PyQt people to respond, _if_ I could manage a > simple example (haven't yet). I would need to debug more, but some incidents in Real Life (well in line with every Debian release -- something always happens when we are close to a stable release) having been draining too much of my time to look properly into this. > The reason that PyQt is involved with IPC at all is that I have to be able > to respond to I/O on the IPC socket in the PyQt/Qt message loop. PyQt > doesn't provide any other services beyond providing a callback when data is > ready to read on the IPC socket. Yuck. There is no easy way around it, then. > Also, should you think the PyQT problem is only related to faxing, well... > >hp-toolbox will spin around at 100% CPU busy loops while waiting IPC > >messages sometimes (it is not locked, it responds well, and if you close > >it, > >the 100% busy loop goes away, and nothing is left stuck). hp-sendfax does > >things that look like this too. The issue is spread all over hplip. > > > We've never seen this behavior (at least in the last year). Is there any > way you could show us how to duplicate it or test it? It seems to be tied to the same problem, you're unlikely to be able to duplicate it unless you are using PyQ 3.15 or 3.16. Note that I recompile all the UI code (and so does Ubuntu, I believe), so that may also help to get the problematic code from PyQT active. I will see if I can find a way to easily and conveniently duplicate the issue, and report back. But it may take at least two days before I can look into it. I recall it had something to do with the hp-toolbox process doing something really dumb with select() in a fd that has pending data that never gets read, I think -- obviously something inside pyqt code, and not hp-toolbox code -- and so it busyloops instead of sleep. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ HPLIP-Devel mailing list HPLIP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hplip-devel
