From: Joe P. <joe...@sn...> - 2001-06-17 04:34:56
|
On Wednesday 13 June 2001 07:19 am, David Paschal wrote: <...> > > > > 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! > > I haven't yet determined with 100% certainty why this happens, but I added > an extra error message after this particular failed call that prints out > some interesting variables. I somehow managed to hit this on the first > try after adding the extra error message, but only once. In my case, the > extra information was "exContext=4, scd=8, state=5". Let me know if you > or anybody else sees this again, especially if becomes reproducible. I'll > try to get to root cause instead of applying a superficial fix that makes > the error go away but doesn't actually fix the underlying problem. > > David Similar error messages appeared in /var/log/messages today. I've included all of the ptal-related messages generated during the session. These startup messages would have been logged at boot. I start ptal-printd and ptal-mlcd from /etc/rc.d/rc.local . Jun 16 09:22:12 tumbleweed ptal-mlcd: ptal-mlcd: SYSLOG at ExMgr.cpp:679, dev=<par:0>, pid=786, errno=111 ptal-mlcd successfully initialized. Jun 16 09:22:12 tumbleweed ptal-printd: ptal-printd(mlc:par:0) successfully initialized. These error messages appear to have been logged shortly after boot. I don't think the printer was in active use at the time. Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:727, dev=<par:0>, pid=786, errno=11 fdRegister(invalid fd=-1,r=1,w=0) called from ExMgr.cpp:2079! Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: ERROR at ExMgr.cpp:2082, dev=<par:0>, pid=786, errno=11 exContext=4, scd=8, state=5! Jun 16 09:26:22 tumbleweed ptal-mlcd: ptal-mlcd: SYSLOG at /home/joe/CVS/hpoj_copy/mlcd/bp/ex/ExMgr.h:540, dev=<par:0>, pid=786, errno=11 ptal-mlcd successfully activated. -- Joe |