NAME
	lpd - off line print daemon


SYNOPSIS
	lpd.acc or lpd.prg


DESCRIPTION

Lpd is a spooling daemon to receive files from a remote lpr client and print them
on a printer attached locally.

Options:
	none


ENVIRONMENT

No environment variables are used


FILES

The following file is consulted by lpd:

printcap in the same directory as lpd.acc or lpd.prg (more precisely: the current directory
when lpd.acc or lpd.prg is invoked)


SEE ALSO

lpr(1), lpq(1), lprm(1), pr(1), printcap(5), lpc(8)


HISTORY

The lpd daemon appeared in 3BSD.


DIAGNOSTICS

This version of lpd has a lot of limitations:

- Spooling:
This version or lpd has no queuing mechanism. Files received over the network
get stored in the spooling directory and then get printed immediately.

- printcap:
In contrast to the usual Un*x lpd which reads printcap for each request, this lpd
reads printcap only when starting up. Thus you usually need to reboot to have changes
in printcap take effect.

- printcap file layout:
The printcap file layout follows the conventional Un*x one with some limitations:
The printer queue name may not contain aliases separated by a vertical bar.
The only items used and mandatory are
	sd=<spool directory>
	lp=<printer device>
other items are ignored.

Example printcap contents:
mydj:sd=c;\tmp:lp=u;\dev\prn

Note that as the colon is used as a field separator in print cap, a semicolon *must* be
used to designate that a TOS drive character is present.

In the above example the printer connected to the parallel port - which is the device
u:\dev\prn under the MagiC operating system - is accessible as the printer mydj from 
the remote computer, e.g. by lpr.ttp -Pmydj <file>
Temporary files get stored in the directory c:\tmp

You may have as many as 5 lines in printcap to designate different printers or
different queue names for the same printer.

No filtering mechanism is implemented. It is assumed print output directed to lpd is 
already in binary format suitable for the printer attached to the printer device.

No flag pages, headers, ... are supported.

In short: all formatting options conveyed by a remote lpr are ignored.
