SAM Idling along

[Simon Waters_2]

Delegated the printer and plotter section using restricted SAM with 10.20.

Came back to find user eating 87% of CPU.

They has set a 30 second refresh for print queue entry information.

The system only has 20 printers - so I can't believe it takes 30 seconds to
check the queue. Is SAM doing something silly here?

No specific SAM patches, although some installed for y2k.

[Dan Hull]

Are there remote printers? They can take a lot longer to report back, but I
don't know why it would take that much CPU in any case. Is this consistently
repeatable?

You may want to consider loading the latest sam and lp patches.

[Simon Waters_2]

It's repeatable.

Yes there is a remote printer. One rlp to a Xerox Document Center.

I guess it is possible it is taking longer than 30 seconds to do the refresh,
and is so getting behind.

I can try removing the remote printer on our test box. See if that is the
culprit.