xref: /titanic_52/usr/src/man/man1m/lpmove.1m (revision 6a1af1a67532df169a657cce07140be64bdea084)
te
Copyright (c) 2006 Sun Microsystems, Inc. All Rights Reserved.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
lpmove 1M "6 Jun 2006" "SunOS 5.11" "System Administration Commands"
NAME
lpmove - move print requests
SYNOPSIS

lpmove [request-ID] destination

lpmove source destination
DESCRIPTION

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 within an instance of a print service, not between a local and a remote queues or local queues on different instances of a print service. Requests can only be moved if the print service or protocol supports it. The LP print server and IPP print protocol both support moving requests between queues. The BSD print protocol does not.

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.

OPERANDS

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, URI-style (scheme://endpoint), POSIX-style (server:destination) syntax.

source

The name of the destination from which lpmove moves all print requests. Specify destination using atomic, URI-style (scheme://endpoint), POSIX-style (server:destination) syntax.

See printers.conf(4) for information regarding the naming conventions for atomic names and standards(5) for information regarding POSIX.

EXIT STATUS

The following exit values are returned:

0

Successful completion.

non-zero

An error occurred.

FILES

/etc/printers.conf

System printer configuration database

$HOME/.printers

User-configurable printer database

ou=printers

LDAP version of /etc/printers.conf

printers.conf.byname

NIS version of /etc/printers.conf

printers.org_dir

NIS+ version of /etc/printers.conf

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPEATTRIBUTE VALUE
Interface StabilityObsolete
SEE ALSO

lp(1), lpr(1B), lpstat(1), accept(1M), lpadmin(1M), lpsched(1M), printers.conf(4), attributes(5), standards(5)

System Administration Guide: Solaris Printing

NOTES

When IPP is in use, the user is prompted for a passphsrase if the remote print service is configured to require authentication.