RE: [hpoj-devel] lots of ptal-mlcd fixes

[PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...>]

Obi-Wan wrote:
> Once I applied Joe's fix so that it would compile, I ran scanimage
> three times in a row.  It passed all tests in about 25 seconds per
> run.  My scanner bed is empty (I'm at work), but scanning a white
> scanner lid seems to work.
Thanks to all who reported the compile error (sorry about that!).  It's
fixed in CVS now, but those of you who modified ExMgr.h should delete that
file before running "cvs update" to prevent a merge conflict.  I guess newer
versions of gcc are stricter about this.

> I also wouldn't mind having it log to the lpr facility 
> instead of daemon
> or whatever, since that seems like the most appropriate place.  Others
> may disagree.
What difference does that make?  Does it cause the messages to get logged
into a different file (according to rules in /etc/syslog.conf)?  The message
itself doesn't actually reflect the facility, and it seems to me that
/var/log/messages is an appropriate file to log into, since that's where the
kernel messages go (useful for debugging USB plug/unplug issues).

Joe Piolunek wrote:
> This appeared in /var/log/messages, I don't seem to recall any failures 
> occurring at the time, though. Unfortunately, I don't recall exactly what
I 
> was doing that led to the errors being logged. I tried to recreate the
errors 
> with no luck.
> 
> Jun 12 19:05:05 tumbleweed ptal-mlcd:  ptal-mlcd: ERROR at ExMgr.cpp:708, 
> dev=<par:0>, pid=1185, errno=11
> Jun 12 19:05:05 tumbleweed ptal-mlcd: fdRegister(invalid fd=-1,r=1,w=0) 
> called from ExMgr.cpp:2056!
Thanks for mentioning that.  I think I have an idea about what the problem
is.

David