apsfilter 6.1.1: [machine reboots after printing, no warning]

[gw <gw@xxxxxxxxxxxxxxxxxxxxxxx>]

Hi -

The printing seems to be -nearly- there, but once a page is finished, the machine reboots.  There isn't any warning, the machine does not go into ddb> mode, there are no coreflies left.  It just reboots.  Of course, once it reboots, lpd thinks there is -still- a job to print, so it tries again.  And reboots.  

Printing ASCII text produces no problems.  Printing ASCII text with simple-minded filters to remove 'stair-stepping' produces no problems.  It is only the more complicated printing that causes the problem.  

I have attached exactly one logfile, which is log.apsf.  

Thanks in advance for any help you can offer.

-Greg White


(1) Some simple questions:

	Operating System  : OpenBSD 2.9
	apsfilter Rel.    : apsfilter-6.1.1
	ghostscript Rel.  : gs 7.00 (make sure with gs -h)
	Printer           : HP LaserJet 4L
	serial/parallel   : parallel printer
	Mono/Color        : mono
	Postscript-Printer: no
	Print Resolution  : Default, 300x300, 150x150
	or                : 
	Your Full Name    : Greg White
	Your e-mail addr  : gw@scientific-biscuits.com

(2) - Problem description
    - what ghostscript printer driver did you use >ljet4<

(3) Any error messages from your operating system, indicating trouble 
    concerning TCP/IP, lpd ? Browse your systems syslog logfiles, i.e.
    /var/log/messages or /var/log/lpd-errs, ...

    from /var/log/lpd-errs:

Sep  3 10:36:38 pointsman lpd[28271]: restarted
Sep  3 12:53:14 pointsman lpd[30631]: restarted
Sep  3 23:09:35 pointsman lpd[29919]: restarted
Sep  4 12:42:35 pointsman lpd[2239]: restarted
Sep  4 12:53:34 pointsman lpd[1889]: restarted
Sep  4 14:00:28 pointsman lpd[19040]: restarted
Sep  4 14:08:11 pointsman lpd[21407]: restarted
Sep  4 14:15:18 pointsman lpd[10057]: restarted
Sep  4 14:54:30 pointsman lpd[31894]: restarted
Sep  4 15:02:07 pointsman lpd[13030]: restarted

There is nothing -at all- in /var/log/messages other than boot messages.

(4) Did you read all help-files ?

	The most important are:
		README, INSTALL, FAQ, TODO, ChangeLog, doc/README.TeX
	If not, then please do so first.

Yes, this problem isn't covered.

(5) Did you enable debugging in the apsfilter shellscript to track down
    simple errors yourself ? For more infos on how to do this, see the FAQ
    file. Please do so first !!!
    If you can't find the problem, then please send me the debugging
    output of *exactly* one print session.

Yes, attached as log.apsf

(6) The printer entry from your /etc/printcap file, that caused trouble,
    i.e. if you have trouble forcing ASCII printing the entry from the
    printer named auto would be fine:

lp|Printer1 auto:\
    :lp=/dev/lpt0:\
    :if=/usr/local/etc/apsfilter/basedir/bin/apsfilter:\
    :sd=/var/spool/lpd/lp:\
    :lf=/var/spool/lpd/lp/log:\
    :af=/var/spool/lpd/lp/acct:\
    :mx#0:

>notice the :sh: was removed!

(7) Did you modify apsfilterrc in /etc/apsfilter and/or in the printer
    specific config directory /etc/apsfilter/NAME ?
    If you modified the file, try printing without the modifications.
    Still problems ?

didn't modify it

(8) Does a private (user defineable) apsfilterrc exist ?
    Please Note: for security reasons only allowed if you defined
    USE_USER_CODE in the global or printer specific apsfilterrc file.
    Is there a  $HOME/.apsfilter/apsfilterrc.NAME  file, if yes does it
    include changes to any configuration variables ?

no.

(9) Is it perhaps a file type recognition problem ?
    The output of your file(1) command on the file that can't be printed:
    i.e. type:	file file_that_can't_be_printed
		file_that_can't_be_printed: English text
    Please uncompress the file before (gunzip, bunzip2 etc).

No, .jpg, .gif, and .ps work, it's what happens after the page is ejected that is the problem.

(10) The part of your printers logfile that logged the commands of
     your failed print session, see lf= in /etc/printcap, i.e.:
	lp|Printer1 auto:\
	...
	    :lf=/var/spool/lpd/lp/log:\
	...
     So you find debugging output in the file
	/var/spool/lpd/lp/log
     This logfile contains debugging data, if you enabled debugging as
     described in the FAQ.
     For LPRng spoolers: depending on the configuration, debugging output
     might also be logged to the "status" file in the spool directory, e.g.
	/var/spool/lpd/lp/status

yes, as discussed above.

(11) Mostly true on Linux Distributions:
     Do you use the traditional printer spooler (lpd)
     or the one that is called LPRng (line printer next generation) ?

Thanks for complete informations !

	Andreas ///

log.apsf