[cups.development] [RFE] STR #2262: lpmove and web 'Move job' to move 'Processing' job as well

John A. Murdie john at cs.york.ac.uk
Mon Feb 26 03:58:06 PST 2007


DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

I find that web page 'Move job' command works as expected when a job is
shown as 'Pending' or is 'Held'. (The lpmove(1) command works similarly ok
as root user; in my test installation I commanded as root on the print
server "/usr/local/pkg/cups-1.2.5/sbin/lpmove -hlocalhost:632 pp23-60
pp00". I'm not convinced that lpmove works at all for an ordinary user,
but I'll report that separately.) When instead the job is 'Processing' the
move is shown to take place but the printout still appears on the original
printer. (When I've been too late with the lpmove command, I've seen the
error message "lpmove: Job #nn is finished and cannot be altered!", which
is good.)

I'd like either that a move of a processing job is forbidden and an error
message (perhaps "Can't move job as it is already printing") to appear, or
the move to be allowed and implemented (perhaps by killing the original
backend) in which case a warning message should appear (perhaps "All or
part of your document may already have been printed on printer xyzzy").
Which of these alternatives should take place might even be offered as a
site-configurable choice.

John A. Murdie

Link: http://www.cups.org/str.php?L2262
Version:  -feature





More information about the cups mailing list