Menu
▾
▴
[hpoj-devel] Re: ptal-printd init script for RedHat (David Paschal)
|
From: Timothy L. <ti...@wo...> - 2000-12-21 02:05:38
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> David Paschal wrote: <blockquote TYPE=CITE>I'm glad you used the .conf file to allow multiple instances of ptal-printd <br>to be invoked. Hopefully the "killproc" function will be able to handle <br>this properly.</blockquote> Yes, I've tested the init script for multiple instances of ptal-printd, and the <b>killproc</b> function kills them all in one go. <blockquote TYPE=CITE>I probably should fix ptal-printd so it cleans up after itself when getting <br>killed, including deleting the pipe.</blockquote> There's one problem I've found with ptal-printd using the initscript. There is another problem related to the loadable modules. The situation goes likes this: <blockquote>ptal-printd will start with the printer off, but if I try to print, it quits. After reading through the source code, it appears that any manner of error will cause ptal-printd to exit. <p>In my opinion, error conditions should be logged, but the daemon should just continue to run. Otherwise the machine will be left in a broken state, thinking the ptal-printd subsystem is running, when in fact the daemon is long gone. <p>Now the problem with the modules. Let's say that I realized my printer wasn't turned on for ptal-printd and it died. So I turned on the printer, then restarted the ptal-printd daemon. Now try printing -- nope, nothing. And ptal-printd dead again. In fact running <b>hpo devid</b> tells me there are no devices available. <p>I tried this another way: with the printer turned on, run <b>hpo devid</b> to coax both <i>ieee12844.o</i> and <i>ieee12844pp.o</i> to load. Now manually remove <i>ieee12844pp.o</i> with <b>rmmod ieee12844pp</b>. Turn off the printer. Then run <b>hpo devid</b> again. There's a message which reports a device is registered to IEEE12844.4 protocol layer, then <i>hpo</i> fails. <p>My question: is the device list fixed for <i>ieee12844.o</i> during loading, or is it updated dynamically? If not, there'll definitely be a problem with OfficeJets that were not turned on during boot up (must remove modules by hand, or wait for cron to clean up autoload modules).</blockquote> Sorry that I sound like such a nag... <grin> But David, thanks again for the great work on hpoj! <p>And Merry Christmas to you all, of course! <smile> <br> <blockquote>Timothy</blockquote> </html> |
