lpmove(8) Apple Inc. lpmove(8)NAME
lpmove - move a job or all jobs to a new destination
lpmove [ -E ] [ -h server[:port] ] [ -U username ] job destination
lpmove [ -E ] [ -h server[:port] ] [ -U username ] source destination
lpmove moves the specified job or all jobs from source to destination. job can be the job ID number or the old destination and job ID:
lpmove 123 newprinter
lpmove oldprinter-123 newprinter
The lpmove command supports the following options:
Forces encryption when connecting to the server.
Specifies an alternate username.
Specifies an alternate server.
SEE ALSO cancel(1), lp(1),
Copyright 2007-2009 by Apple Inc.
12 February 2006 CUPS lpmove(8)
Check Out this Related Man Page
lpmove(1M) System Administration Commands lpmove(1M)NAME
lpmove - move print requests
lpmove [request-ID] destination
lpmove destination1 destination2
The lpmove command moves print requests queued by lp(1) or lpr(1B) between destinations.
The first form of lpmove moves specific print requests (request-ID) to a specific destination.
The second form of the lpmove command moves all print requests from one destination (destination1) to another (destination2). This form of
lpmove also rejects new print requests for destination1.
lpmove moves individual requests or entire queues only between local printers or between remote printers, not between a local and a remote
printer. You can move only requests that were not previously transferred to the server.
When moving requests, lpmove does not check the acceptance status of the destination to which the print requests are being moved (see
accept(1M)). lpmove does not move requests that have options (for example, content type or requiring a special form) that cannot be handled
by the new destination.
The following operands are supported:
request-ID The specific print request to be moved. Specify request-ID as the identifier associated with a print request as reported by
lpstat. See lpstat(1).
destination The name of the printer or class of printers (see lpadmin(1M)) to which lpmove moves a specified print request. Specify
destination using atomic, POSIX-style (server:destination) syntax.
destination1 The name of the destination from which lpmove moves all print requests. Specify destination using atomic, POSIX-style
destination2 The name of the destination to which lpmove moves all print requests. Specify destination using atomic, POSIX-style
See printers.conf(4) for information regarding the naming conventions for atomic names and standards(5) for information regarding POSIX.
The following exit values are returned:
0 Successful completion.
non-zero An error occurred.
/var/spool/print/* LP print queue.
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWpcu |
SEE ALSO lp(1), lpr(1B), lpstat(1), accept(1M), lpadmin(1M), lpsched(1M), printers.conf(4), attributes(5), standards(5)
System Administration Guide: Advanced Administration
SunOS 5.10 8 Feb 2001 lpmove(1M)
I would like to know how to move jobs from one print queue to another. I'm learning a system based on SCO Unix and I found a way to assign a good printer queue to a damaged printer but it's only good for future jobs. The jobs that hit the queue of the bad printer are stuck in there. Is there a way... (3 Replies)
I am trying to let user asillitoe su to the godbrook role to execute commands. I have editted files as follows:
Gadbrook:::Allow root commands to be used by godbrook:
exec_attr:... (0 Replies)
I'm trying to install a newer version of CUPS and my compilation fails:
checking for gawk... gawk
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling...... (4 Replies)
Sorry for my english!
I'm using Debian squeeze and for an assignement, i have create 2 virtual pdf cups printers. Both are working very well.
To test the different administion command; i try to disable one of the printer and move his queue file to the second one. I'm able to do it easily.
... (4 Replies)