11-01-2018
this appears to use the lpr/lpd protocol. in this case the print file is stored in /usr/spool/lpd/destination and from there directly transferred to the device.
do you have netcat on your system or know if a binary is available.
you could stop the print service and manually edit the print file then restart the service.
do you know what unix release this is and if it is binary compatible with anything.
5 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I registered a printer hp123 on Sun Solaris Server.
I think my printer is expecting a carriage return and linefeed combination at the end of each line (DOS standard), but unix files only have linefeeds at the end of each line.
How can I configure the lp system to filter files passed to it?... (1 Reply)
Discussion started by: simt
1 Replies
2. AIX
Hello..
Plz, Any one can help me ?
when I execute a printing system with the command lp -d<name of printer>, no result with all printers.
I have verified the three processes : qdaemon, lpd, writesrv (No problem).
thank's (0 Replies)
Discussion started by: okbainf
0 Replies
3. Shell Programming and Scripting
I have a problem with the following skript in awk.
cat runde.txt |awk '{
if ($5==2) {
dataname_v=$1 "_" $4 "_adjust.rad
befehl1="gensurf seitenwand... (17 Replies)
Discussion started by: ergy1983
17 Replies
4. Solaris
Hello folks,
I'm currently working on migration of printing system from one server to another (namely from Sol 9 to Sol 10).
I would like ask if is possible to manage migration via simple copying /etc/printers.conf file and folder /etc/lp to the new server??? I'm not sure if printers... (2 Replies)
Discussion started by: brusell
2 Replies
5. Shell Programming and Scripting
I have a file contains data with non-printing characters. i have used cat -v filename to display whole data with non-printing characters also.
However, i need lines with non-printing characters into seperate file. My file is huge and looks like i have to manully find lines using cat -v filename |... (3 Replies)
Discussion started by: JSKOBS
3 Replies
in.lpd(1M) System Administration Commands in.lpd(1M)
NAME
in.lpd - BSD print protocol adaptor
SYNOPSIS
/usr/lib/print/in.lpd
DESCRIPTION
in.lpd implements the network listening service for the BSD print protocol specified in RFC 1179. The BSD print protocol provides a
remote interface for systems to interact with a local spooling system. The protocol defines five standard requests from the client to the
server: starting queue processing, transfering print jobs, retrieving terse status, retrieving verbose status, and canceling print jobs.
in.lpd is started from inetd. See inetd(1M). inetd waits for connections on TCP port 515. Upon receipt of a connect request, in.lpd is
started to service the connection. Once the request has been filled, in.lpd closes the connection and exits.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
non-zero An error occurred.
FILES
/etc/printers.conf
System printer configuration database.
printers.conf.byname
NIS version of /etc/printers.conf.
printers.org_dir
NIS+ version of /etc/printers.conf.
/usr/lib/print/bsd-adaptor/bsd_*.so*
Spooler translation modules.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWpcu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), inetadm(1M), inetd(1M), svcadm(1M), printers.conf(4), attributes(5), smf(5)
NOTES
The in.lpd service is managed by the service management facility, smf(5), under the service identifier:
svc:/network/lp
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibil-
ity for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view config-
uration information for this service. The service's status can be queried using the svcs(1) command.
SunOS 5.10 5 Aug 2004 in.lpd(1M)