Is there a way to kill a bad cups print job? Yesterday I lpr'd a text file, with a .py suffix, and page after page of a few lines of funny characters started coming out of my HP deskjet 855c. Somehow I suppose it was sending postscript and the printer "thought" is was plain ascii. I couldn't kill the print job. I tried: 1. lprm <jobnumber> 2. rccupsd stop 3. LPC (but LPC is emasculated under cups) 4. the web interface to cups-the job was "finished" according to it, , because of (1) but I "stopped" the printer anyway. This had no effect. 5. killed the two cups daemon processes running, despite (2) 6. erased everyting in /var/spool/cups and /var/spool/lpd 7. unplugged the parallel cable from the printer 8. unplugged (not just turned off) the printer (I should have looked for rogue spool files in /tmp but I didn't think of this). All of the above had no effect at all. Plugging the printer back in and attaching the cable STILL led to over 100 pages of garbage: I sat there and refed the same 20 sheet through again and again. There was nothing in my process table that I could identify that was doing this, i.e. no cups.... and no lp.... processes. Can someone tell me what I should or could have done? I "solved" the problem by getting rid of cups and installing lprng, which I have done every time SuSE has installed cups for me, but there must be a less drastic way. Thanks, Henry Harpending