LPD and sophisticated documents


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers LPD and sophisticated documents
# 1  
Old 03-30-2006
LPD and sophisticated documents

Hi all,

I am using Solaris 8 and have several printers (HP lasers or inkjets) connected behind PCs, printing thus being controlled by LPD.
All I can print is ASCII, not very keen, no images, no boxes etc.
Is there any thread (I assure, I have been searching!) or discussion explaning how to set up printers to be capable of printing more sophisticated docs?
It seems (?) that LPD is taking the document as it comes but I have also a labelprinter (Zebra) accepting its own control language and capable of printing barcodes etc. and connected in the same way.

Thanks in advance! Smilie

Peter
 
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Verifying LPD is running

Apologies in advance, I'm usually a Linux admin so I'm not well versed in Solaris administration. In Linux there's usually an lpd executable running and you can check the process list for it to do a high level check on the state of the printing subsystem. Is the executable called the same in... (1 Reply)
Discussion started by: thmnetwork
1 Replies

2. SCO

Replace Line Printer Daemon (LPD) with CUPS

hi Howto replace Line Printer Daemon (LPD) with CUPS on SCO 5.0.6? (3 Replies)
Discussion started by: ccc
3 Replies

3. SCO

LPD PRINTER CONFIGURATION

Dear All, I have configured a printer on a unix box to be printing on windows xp printer. Below are the steps followed:- Create the printer on the Windows XP box and share it as prt5 Enable unix printer services on windows XP box On unix box i make changes on hosts,hosts.equiv and .rhosts... (1 Reply)
Discussion started by: njoroge
1 Replies

4. SCO

lp: cannot lock /usr/spool/lpd/printer1/.seq

Hi. I'm receive thats error on my PC. lp: cannot lock /usr/spool/lpd/printer1/.seq This PC is a Windows pc running lpd on port 515. That its means? Thanks. PD. Sorry for my english! (0 Replies)
Discussion started by: sebpes
0 Replies

5. UNIX for Dummies Questions & Answers

restarting lpd service question

Hi, Im wondering, if I do a restart of my lpd service, will it clear the print queue? Or will the file in queue will still be there after the restart? Thank you (1 Reply)
Discussion started by: Nayas
1 Replies

6. UNIX for Dummies Questions & Answers

lpd printing and a IP based printer on SCO

I am attempting to setup an IP based printer in a SCO environment. It is a cognitive printer. I attempted to add it via the HP interface but I could not get anything sent from the spooler to the printer in SCO? My questions is or are should this be setup as a local or remote printer? When I... (6 Replies)
Discussion started by: spglass
6 Replies

7. Solaris

sudo documents

I have installed sudo on our development server (SPARC,Solaris 9) and trying to edit /etc/sudoers file using visudo. Referred the following sites and not able to find the way. http://www.courtesan.com/sudo/man/sudoers.html http://www.kempston.net/solaris/sudo.html To start with sudo, my... (3 Replies)
Discussion started by: chrs0302
3 Replies
Login or Register to Ask a Question
cups-lpd(8)							    Apple Inc.							       cups-lpd(8)

NAME
cups-lpd - receive print jobs and report printer status to lpd clients SYNOPSIS
cups-lpd [ -h hostname[:port] ] [ -n ] [ -o option=value ] DESCRIPTION
cups-lpd is the CUPS Line Printer Daemon ("LPD") mini-server that supports legacy client systems that use the LPD protocol. cups-lpd does not act as a standalone network daemon but instead operates using the Internet "super-server" inetd(8) or xinetd(8). If you are using inetd, add the following line to the inetd.conf file to enable the cups-lpd mini-server: printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd -o document-format=application/octet-stream Note: If you are using Solaris 10 or higher, you must run the inetdconv(1m) program to register the changes to the inetd.conf file. If you are using the newer xinetd(8) daemon, create a file named /etc/xinetd.d/cups containing the following lines: service printer { socket_type = stream protocol = tcp wait = no user = lp group = sys passenv = server = /usr/lib/cups/daemon/cups-lpd server_args = -o document-format=application/octet-stream } OPTIONS
-h hostname[:port] Sets the CUPS server (and port) to use. -n Disables reverse address lookups; normally cups-lpd will try to discover the hostname of the client via a reverse DNS lookup. -o name=value Inserts options for all print queues. Most often this is used to disable the "l" filter so that remote print jobs are filtered as needed for printing; the examples in the previous section set the "document-format" option to "application/octet-stream" which forces autodetection of the print file format. PERFORMANCE
cups-lpd performs well with small numbers of clients and printers. However, since a new process is created for each connection and since each process must query the printing system before each job submission, it does not scale to larger configurations. We highly recommend that large configurations use the native IPP support provided by CUPS instead. SECURITY
cups-lpd currently does not perform any access control based on the settings in cupsd.conf(5) or in the hosts.allow(5) or hosts.deny(5) files used by TCP wrappers. Therefore, running cups-lpd on your server will allow any computer on your network (and perhaps the entire Internet) to print to your server. While xinetd has built-in access control support, you should use the TCP wrappers package with inetd to limit access to only those comput- ers that should be able to print through your server. cups-lpd is not enabled by the standard CUPS distribution. Please consult with your operating system vendor to determine whether it is enabled on your system. COMPATIBILITY
cups-lpd does not enforce the restricted source port number specified in RFC 1179, as using restricted ports does not prevent users from submitting print jobs. While this behavior is different than standard Berkeley LPD implementations, it should not affect normal client operations. The output of the status requests follows RFC 2569, Mapping between LPD and IPP Protocols. Since many LPD implementations stray from this definition, remote status reporting to LPD clients may be unreliable. SEE ALSO
cups(1), cupsd(8), inetconv(1m), inetd(8), xinetd(8), http://localhost:631/help COPYRIGHT
Copyright 2007-2011 by Apple Inc. 4 August 2008 CUPS cups-lpd(8)