summaryrefslogtreecommitdiffhomepage
path: root/printutils
diff options
context:
space:
mode:
authorDenis Vlasenko <vda.linux@googlemail.com>2008-03-24 02:18:03 +0000
committerDenis Vlasenko <vda.linux@googlemail.com>2008-03-24 02:18:03 +0000
commitc693840fe81e59a308e0c6e3d2bafae728d1caff (patch)
tree10924edda7796e5242e460364c2f3587f2841c0f /printutils
parent42cc304e9084843ad6b153afaf4b3f6c6528c364 (diff)
*: whitespace fixes, no code changes
Diffstat (limited to 'printutils')
-rw-r--r--printutils/lpd.c20
1 files changed, 10 insertions, 10 deletions
diff --git a/printutils/lpd.c b/printutils/lpd.c
index bc0348eba..4008e4396 100644
--- a/printutils/lpd.c
+++ b/printutils/lpd.c
@@ -18,13 +18,13 @@
* and should have the following structure:
*
* SPOOLDIR/
- * <queue1>
- * ...
- * <queueN>
+ * <queue1>
+ * ...
+ * <queueN>
*
* <queueX> can be of two types:
- * A. a printer character device or an ordinary file a link to such;
- * B. a directory.
+ * A. a printer character device or an ordinary file a link to such;
+ * B. a directory.
*
* In case A lpd just dumps the data it receives from client (lpr) to the
* end of queue file/device. This is non-spooling mode.
@@ -38,11 +38,11 @@
* lpd only sanitizes them (by removing most non-alphanumerics).
*
* If HELPER-PROG (with optional arguments) is specified then lpd continues to process client data:
- * 1. it reads and parses control file (cfA...). The parse process results in setting environment
- * variables whose values were passed in control file; when parsing is complete, lpd deletes
- * control file.
- * 2. it spawns specified helper application. It is then the helper application who is responsible
- * for both actual printing and deleting processed data file.
+ * 1. it reads and parses control file (cfA...). The parse process results in setting environment
+ * variables whose values were passed in control file; when parsing is complete, lpd deletes
+ * control file.
+ * 2. it spawns specified helper application. It is then the helper application who is responsible
+ * for both actual printing and deleting processed data file.
*
* A good lpr passes control files which when parsed provide the following variables:
* $H = host which issues the job