Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!ucbvax!RAND.ORG!guyton%condor
From: guyton%condor@RAND.ORG
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP/papif question
Message-ID: <8912080159.AA00486@condor.rand.org>
Date: 8 Dec 89 01:59:51 GMT
References: <1989Dec7.201124.5674@agate.berkeley.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

Another useful trick with papif is to make the filter a shell
script.  We have:

	if=/usr/local/cap/rover

but "/usr/local/cap/rover" isn't a link to papif, but instead
is a shell script containing:

	#!/bin/sh
	DEBUG=1
	export DEBUG
	/usr/local/cap/papif -P rover $* > test.log 2>&1


This lets you monitor the output from the printer (called "test.log"
in the spool directory).  Useful for tracking down the occasional
postscript errors.

-- Jim Guyton
   guyton@rand.org