michaelrsweet
commented
21 years ago CUPS.org User: mike
Unlike LPR or LPRng, CUPS does not query the remote server for a list of its jobs; you will only see a local view of jobs that are pending on the remote queue. This is by design and will not be changed.
To duplicate the functionality of LPR or LPRng, set the ServerName directive in the client.conf file and don't run a local scheduler.
Version: 1.1.19rc5 CUPS.org User: pwaltman.eecs.tufts.edu
I have 2 cups servers running. One on a solaris box (SunOs 5.7) which is a compiled version of cups v.1.19. the second is on a RH 9 box with a rpm package version of cups 1.19rc5.4.
cupsd on the solaris box browses the queues on the RH9 box via the BrowsePoll directive in the cupsd.conf file. cupsd on the solaris box will print to the queues on the rh9 box with cups' lp commands, however, lpq -P will not list the jobs that are in the queue. It will report whether the queue is active or not, but none of the waiting jobs are listed.
if logged onto the solaris box, 'lpq -P ...' for queues local to the solaris box will be reported correctly. 'lpq -P' also works correctly on the rh9 box. I checked the list and saw the bug about lpq crashing on v.1.19rc5 with 'lpq -P ...' requests, but this behavior does not occur on the 1.19rc version I have running on the rh9 box.
I get similar behavior from another rh 9 client (using cups v.1.17) which browses the solaris box. when querying via 'lpq -P...' for info on a queue local to the solaris box, the waiting jobs are not reported.
I apologize if this is a config problem on my side, but the fact that print jobs are passed and print correctly between all the clients to the