My jobs stay in the queue after printing

My platform :
- Two Sun Sparc stations, the first is Print Server, the second is Print Client.
- They are linked via Ethernet.
- My HP LaserJet Printer is connected in parallel on bpp0 of the Print Server.
- System : Solaris 2.5.1

When I print from Print client, printing is good but my jobs stay in the queue
after printing. (lpc command says : "nn jobs in spool ..").
Can you tell me how to stop this problem ?

NOTE : when I use command "lpstat -t", the queue is cleared (0 job in spool).
jpprigAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

darreningsCommented:
I have seen this before on Sun's. As Solaris is a System V Rel 4 Unix, then I would use the lpstat -t command to check the queue. This will provide the correct information. The lpc and lpq commands are throw backs for Sun OS (not System V Rel 4), I belive this is a bug and I'm sure I remeber phoning Sun about this and them saying that this was a bug.
Check with Sun support on this, is you have it - but I suggest using lpstat commands.
I hope this helps.....

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
OMCommented:
I am affraid the answer is not correct ! I have the smae problem : lpstat says ok, although lpc status pr says "74 entries
in spool area" AND I effectively have 74 entry in /var/spool/lp/temp.
The jobs are not removed once printed, and it is not a bug
from lpc !!
I guess this comes from the lack of back communication between
print server and print client.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.