On 12/14/09 01:03 PM, Norm Jacobs wrote: > Stephen Green wrote: >> Hi folks. I'm running snv_127 and using CUPS as my printing system. >> I've been having some trouble printing, so I sat down tonight to take >> a look at it. I followed the advice in: >> >> http://defect.opensolaris.org/bz/show_bug.cgi?id=12719 >> >> and replaced the USB backend. This allowed me to add my LaserJet 1020 >> printer and print a test page. I can also share the printer and use it >> from my wife's MacBook. So far, so good. >> >> The problem that I'm having is that CUPS is really, really (really!) >> slow for me. When using the Web interface at http://localhost:631, >> some operations (e.g., loading the admin page) can take longer than a >> minute to complete. By contrast, the CUPS subsystem on the Mac does >> this in less than a second. >> >> Printing a test page from my wife's Mac to the Solaris box just took >> about 10 minutes (and it got an error printing the CUPS graphic, but I >> think that's probably something else). >> >> Even the command line programs are slow. lpq can take more than a >> minute to run. Is this something that other folks have encountered? Is >> there anything that I can do to help diagnose the problem (e.g., >> trussing cupsd while it's printing or capturing the printing traffic?) > That seems odd to me. I am not seeing (and haven't seen) any delays like > you are reporting. You might try turning up the logging > $ pfexec cupsctl LogLevel=debug2 > and taking a look at the error log (/var/log/cups/error_log). It will > give you some idea of what's going on and when.
Done, then I printed a three page PDF. Of course, now it's working fine! I'll leave the debug on and bang on it a bit more tonight. > There are a bunch of > things that could affect performance. Is you system resource starved? > Are you using and nameservers (NIS, DNS, ...) that it may be having > trouble contacting? I don't think so. The machine is an i7 920 with 12GB of RAM that's not doing much more than showing my Gnome desktop when this is happening, so I don't think it's a resource issue (unless the printing needs a lot of resources :-) Steve Green
