Wiki code for PAPI Client Commands

Hide Line numbers
1: == PAPI Client Commands
2: 
3: === //Delivered in Solaris Nevada build 44//
4: 
5: ====  What are they ?
6: 
7:  Since their beginning, the printing commands have been tied to a specific print system because they have been implemented on top of print system specific protocols and interfaces. This is true of BSD 4.x LPR, [[SysV LP>>http://cvs.opensolaris.org/source/xref/usr/src/cmd/lp/]], [[LPRng>>http://www.LPRng.org/]], [[CUPS>>http://www.cups.org/]], and more. With the recent introduction of the FSG OpenPrinting [[Open Standard Print (PAPI)>>http://sf.net/projects/openprinting]], it is now possible to move these commands on top of a print service/protocol neutral interface. Currently, the PAPI include enough functionality to support replacement of the following commands:
8: 
9: |**Command
10: **|**Origin
11: **|**Description
12: **
13: |[[lpr(1b)>>attach:lpr.1b.html]]
14: |BSD
15: |Submit print jobs
16: |[[lpq(1b)>>attach:lpq.1b.html]]
17: |BSD
18: |Query print queues/jobs
19: |[[lprm(1b)>>attach:lprm.1b.html]]
20: |BSD
21: |Remove print jobs
22: |[[lpc(1b)>>attach:lpc.1b.html]]
23: |BSD
24: |Control print queues (accept/reject/enable/disable/status/clear/topq)
25: |[[lp(1)>>attach:lp.1.html]]
26: |SysV
27: |Submit print jobs
28: |[[lpstat(1)>>attach:lpstat.1.html]]
29: |SysV
30: |Query print service (queues/jobs/other)
31: |[[cancel(1)>>attach:cancel.1.html]]
32: |SysV
33: |Remove print jobs
34: |[[lpmove(1m)>>attach:lpmove.1m.html]]
35: |SysV
36: |Move jobs between local queues
37: |[[accept(1m)>>attach:accept.1m.html]]
38: |SysV
39: |Enable queueing of print jobs on a queue
40: |[[reject(1m)>>attach:reject.1m.html]]
41: |SysV
42: |Disable queueing of print jobs on a queue
43: |[[enable(1m)>>enable.1m.html]]
44: |SysV
45: |Enable job processing on a queue
46: |[[disable(1m)>>disable.1m.html]]
47: |SysV
48: |Disable job processing on a queue
49: 
50: ==== Destination Names
51: 
52: Each of the printing commands listed above takes a printer/queue/destination name as at least one of it’s arguments.  These destination names can be specified in one of three forms:
53: 
54: |Atomic (simple)
55: |(destination) is resolved by locating a //printer-uri-supported// key/value pair for the named destination in the printers.conf(4) or printers(4) configuration database. (If no //printer-uri-supported// key is found for an entry, it’s //bsdaddr// value is converted to printer uri form and used.)
56: |Printer URI
57: |(scheme://endpoint)  is completely resolved and specifies the protocol and communication endpoint to contact for print services.  This form of destination name is useful for accessing print services outside of your system’s current management domain.  Since the name includes the protocol to use when contacting the print service, you can select a richer protocol than the RFC1179 protocol.
58: |POSIX
59: |(server:queue[:extensions]) is complete and resolves to an equivalent printer URI form of lpd://server/printers/queue[#extensions]
60:  This form is being maintained for Solaris backward compatability only.  "Printer URI" form is the preferred replacement.
61: 
62:  Printer URI formats currently supported include the following:
63: 
64: |lpsched
65: |**lpsched://localhost/printers/queue**
66: |This printer uri scheme can only be used to contact a local LP service to access the queue named in the uri.
67: |lpd
68: |**lpd://localhost/printers/queue[#extensions]**
69: |This printer uri scheme can be used to contact local or remote print services to addess the named queue on the named host in the uri.  The optional "#extensions" can be specified as "#solaris" to indicate that the server host will process Solaris extensions to rfc-1179 during job submission.
70: |ipp
71: |**ipp://server[:port]/printers/queue**
72: ******http://server:631/printers/queue**
73: ******ipp://server[:port]/...**
74: |This printer uri scheme can be used to contact local or remote print services to address a particular queue on the named host in the uri.   The "ipp" uri scheme is specified in the Internet Print Protocol specifications and is actually much more free form that listed above.  All Solaris and CUPS based print queues will be accessed using the formats listed above.  Access to print queues on other IPP based print servers requires use of the server supported ipp uri format.  Generally, it will be one of the formats listed above.
75: 
76: ==== Some additional information
77: 
78: * As a result of layering these changes, the following commands will no longer need to be installed SUID root:
79: 
80: /usr/bin/lp, /usr/bin/lpstat, /usr/bin/cancel, /usr/bin/lpmove,
81:  /usr/{ucb|bin}/lpr, /usr/{ucb|bin}lpq, /usr/{ucb|bin}/lprm,
82:  /usr/lib/print/printd.
83: 
84: In the past, they were installed SUID root because they needed some elevated privilege to either open a reserved port,  allocate a sequential job-id number, or maniplate files in /var/spool/print.  Since this functionality has been localized into a small "helper" application (/usr/lib/print/lpd-port), applications using RFC1179 based PAPI support no longer need elevated privilege.  lpd-port contains minimal support for passing RFC1179 protocol requests on a reserved port and allocating sequential job-id numbers.  While it is installed SUID root, it temporarily drops all elevated privilege until the moment that they are needed.  When needed, the privilege is elevated for the required operation and perminently dropped if it is no longer required.  On Solaris, this is done through the use of privileges(5).  On other platforms, this is done using setuid/seteuid/setreuid().
85: 
86: * If you have a local printer and don’t want to share it with anyone on the network, you can now safely disable the printing network listeners
87: 
88: # svcadm disable application/print/ipp-listener \
89:                              application/print/rfc1179 (lpd-listener)
90: 
91: * If you have a Solaris 9u6 or later server, or a CUPS server, lpstat will provide you with more information about remote print queues (and jobs), as well as their capabilities when you use IPP to talk to those servers.
92: * It is now possible to accept, reject, enable and disable remote print queues with proper authorization when IPP is in use (more on this to follow)
93: * It is now possible to remotely move jobs between queues on a print server when IPP is in use.
94: * It is now possible to modify your print jobs remotely when IPP is in use. (eg. submit your job held, change the number of copies, turn on duplexing and release it for printing)
95: 
96: ==== Where can I get access to the bits ?
97: 
98: |[[install-papi-commands.sh>>attach:install-papi-commands.sh]]
99: |A simple shell script to upgrade several printing related packages on your system to include replacement print commands.
100: |[[remove-papi-commands.sh>>attach:remove-papi-commands.sh]]
101: |A simple shell script to remove upgraded printing packages and replace them with Solaris Nevada build 35 packages.  If you want to
102:  match your installation, you will need your installation media.
103: |[[papi-i386.pkgs>>attach:papi-i386.pkgs]]
104: [[papi-sparc.pkgs>>attach:papi-sparc.pkgs]]
105: |A stream format package file containing upgraded printing packages that include replacement print commands laywered on top of the PAPI
106: |[[nv35-i386.pkgs>>attach:nv35-i386.pkgs]]
107: [[nv35-sparc.pkgs>>attach:nv35-sparc.pkgs]]
108: |A stream format package file containing Nevada build 35 printing packages without any replacement print command implementations
109: 
110: ==== Where is the Code ?
111: 
112: Currently, the project is housed on SourceForge at [[http://sf.net/projects/openprinting/>>http://sf.net/projects/openprinting/]] The code contained in the SourceForge project includes a complete implementation of the PAPI with support for interaction with RFC-1179 based print services, as well as IPP based print services. Also included in that code base is and Apache module that implements server side support for IPP on top of the PAPI. The OpenSolaris code base contains [[PAPI support for local LP>>http://cvs.opensolaris.org/source/xref/usr/src/cmd/lp/lib/papi]] interaction. Though much of the work in the SourceForge project is already delivered with Solaris, this project is focusing on delivering the client commands support already in the code base as replacements for the current implementations that are tied directly to either lpsched or the rfc-1179 protocol.
113: 
114: ==== How can I get Involved ?
115: 
116: The OpenPrinting project, currently hosted at SourceForge ([[http://sf.net/projects/openprinting/>>http://sf.net/projects/openprinting/]]), is where implementation work is being done for the PAPI.  If you are interested in support for other print systems, or extending the API, that is probably a good place to start.  Any work to extend the API will at least be prototyped there before rolling it back into the PAPI standard.
117:  You will also find pre-built RPM and dpkg(.deb) packages for Linux systems that and be installed in /opt/papi on a Linux system.  Since the naming support native to Solaris is emulated on the Linux systems, it’s not as complete as what’s available on Solaris.  However, it does contain files and NIS support for printing configuration lookup.
118:  If you run some other OS, you should be able to build the code with little or no effort.  For the most part, the code makes use of POSIX interfaces.  The only significant exception is in the RFC1179 support, were there is code to pass file
119:  descriptors between processes (child to parent).  The code to do so is ifdef’d with support for SysV, BSD 4.3, and BSD 4.4 (also Linux) methods of doing this.
OpenSolaris

Top Menu

Wiki code for PAPI Client Commands

Search

Collectives

Community Group

Project

User Group

Subsites

Community Group printing Pages
