[Darkstream]

Here's one for you. I'd love to know a solution for it. I sent this to Breen but it's happened again today so I figured I'd post here as well.
I've got an Epson Stylus R320 set up on a Mac with printer sharing turned on so all macs on the WiFi network can print to it. Works as it should. So far so good.
But recently I had a job that wouldn't go away when I deleted it from the queue. No matter how many times I stopped the jobs and deleted the file, as soon as I let the printer receive files again the deleted file would reappear and start printing again. Rebooting didn't work. Logging into root to delete the job didn't work. I even accessed the nifty CUPS web interface (http://http://127.0.0.1:631/) and received errors when trying to delete the job.
I eventually had to delete the printer and reinstall it. Even then the queue returned from the dead and my Mac wanted to know if I wanted to use the old one or create a new one. Once I created a new queue the print job finally passed on to Binary Heaven.
Here's my question: Is there a more elegant way to solve this problem WITHOUT deleting the printer? Also, where on earth is that queue located on my Mac? No amount of googling or spotlighting located the queue for me. I'm betting this is an odd network permissions problem. The job in question originated on another Mac.

[aphayton]

Did you try deleting the job from the other mac?

[Darkstream]

<i>Did you try deleting the job from the other mac?</i>
Yes. I made sure there was no job on the other mac. The problem is on the Mac with the printer.
The printer was on. The Mac with the printer was taken off the airport network to isolate it from the other Mac. The other Mac was shut off. The Mac with the printer was rebooted, applejacked (had it's permissions repaired and caches flushed), and prayed over by a troupe of traveling monks. But nothing would make the job go away. Then one day, inexplicably, the job stayed dead.
I'm still looking for a better solution than hoping the printer fairy visits me again. /forums/ubbthreads/images/graemlins/wink.gif

[Nobody]

I think the elegant method to keep the print job from coming back in queue is to save the file(s) you trying to print and then delete from queue.

[Darkstream]

Delete from the queue!?! Did you even read my first post? That's what I can't do. LOL
Let me reiterate: the jobs will not stay deleted. They return from the dead like zombies. The only jobs that won't die are network jobs. My best guess is that this is a permissions problem. For whatever reason jobs are being created that I don't have permission to delete, so they keep coming back. The only solution so far has been to either delete the printer and reinstall it or just let the job print. I still would like to be able to kill any job I change my mind on. That's the whole purpose of the print manager, after all.
Does anybody know where the queue is being kept in Mac OSX? It's not in the obvious places so I can't simply fire up Terminal and chmod the files then rm them.

[Nobody]

I think I meant the somewhat simple two steps to take for the print job removal. The first step is to Save or Save As by double clicking file to open file. This would change the menu bar to the application used to create the file. It might be as simpe as Text Edit. Under the File menu options(or called popup) options list there are Save or Save As options. Select either to save file. This the intuitive end where the system won't let you delete when in the print app.
The second step is to go into the Print & Fax app window and delete the print job. Your file is still in the system where you saved it.
The confusion seemed you created the file from an aplication like Text Edit and went on ahead did a print job of the file. When the print job was done you decided to just delete the file from the Print Queue. The Mac won't let you. You seemed confused. You could have been in the same situation if you needed the file again.
That's how I see it. That's how it 's done.
It's a good idea to save the file after finishing up. Name the file and place where you could find and use again. Get it!!!!

[Damien]

You've already stated the answer to the problem yourself but don't realize it. If the only print jobs that won't delete from your queue are network print jobs, then the problem is clearly that one of the computers on your LAN is continuing to send and re-send a print job(s) to the computer that's set up as the "print server".
So, identify which computer is sending the job(s) and delete the print job from that computer's local print queue so it won't keep sending it to the network print queue set up on the "print server".
I know you say you've done this, but please check again. I can't think of any other reason to explain the behavior your seeing.
If still nothing, then you might try using Print Setup Repair to reset your CUPS settings to default and delete all the printing-related cache files.

[Nobody]

In reply to:

---

Does anybody know where the queue is being kept in Mac OSX? It's not in the obvious places so I can't simply fire up Terminal and chmod the files then rm them.

---

It is a lousy way of deleting print jobs(files). You would never give oneself a second chance. That method probably belongs to Microsoft set of rules.
If you don't don't save at first, you would be in for a big surprise!!!!! Make that a really bad jolt.