Adding new printer messes up existing printer

BradF — Thu, 23 May 2002 14:01:37 GMT

During a DR test I added a new printer to a k360 running HP-UX 11.0 with sam.

When I did a lpstat -v the first printer listed had the same information as the newly added printer.

I.E.
Before:
device for p001: /dev/null
remote to: p001 on print_server1
device for p002....
Add p099
device for p001: /dev/null
remote to: p099 on print_server1
.....
device for p099: /dev/null
remote to: p099 on print_server1

I had this happen before and ended up removing all the printers and re-adding them. The DR test is over so I don't have the machine available.

Has anyone had this happen to them? Is it a printer or sam patch issue?

Thanks,
-Brad

Re: Adding new printer messes up existing printer

Steve Steel — Thu, 23 May 2002 14:06:11 GMT

Hi

This should be a problem fixed by a spooler patch.

One fixed bug is

lpstat was giving the incomplete status because,
it was not searching for the printers/classes from
the begining of the status (pstatus, qstatus) files.

probably printer was ok but badly shown

Steve Steel

topic Adding new printer messes up existing printer in Operating System - HP-UX

Adding new printer messes up existing printer

Re: Adding new printer messes up existing printer