Note: please don't spam any of the e-mail addresses which you see here. Follow this link if you want some addresses to misuse.
From: "David S. Chappell" <David.Chappell@mail.trincoll.edu> Date: Wed, 16 Feb 2000 10:29:40 -0500 Subject: Re: PPR: ppr refuses to print At 11:23 PM 02/15/2000 -0700, Christopher Patricca wrote: >What happens is that the job is seemingly submitted successfully to pprd >but it never gets to the printer. It just sits there in the que never >printing. Is the jobs status "printing" or "waiting for printer"? What is the status of the printer (as revealed by "ppop status lasermaster")? If the printer is in a fault state, what does "ppop alerts lasermaster" say went wrong? >Printer name: lasermaster >Interface: simple >Address: "/dev/lp0" I wonder if you have set the permissions on /dev/lp0 so that the user ppr can write to it. If you haven't the printer will have gone into the "fault, no auto retry" state and "ppop alerts" will contain a message indicating that permission to open /dev/lp0 was denied. The "simple" interface is very simple indeed. For example, if the printer is off line, it will just sit there trying to write data. In contrast, the Linux version of the "parallel" interface in PPR 1.40b2 will report to PPR that the printer is off-line so that the fact can be noted in the "ppop status" output. If you are setting up PPR for the first time, I would recomend 1.40b2 over 1.32p1. The new version is at the very end of the beta testing stage. It is almost certainly more reliable and less buggy than 1.32p1. If I don't hear anything bad about it by the middle of next week, I am going to release it as 1.40. ================================================================ David Chappell David.Chappell@Mail.Trincoll.Edu Computing Center PostMaster@Mail.Trincoll.Edu Trinity College (860) 297-2114 Hartford, Connecticut 06106