ports/54875: hpijs loops on fatal error

Alan Batie alan at batie.org
Sat Jul 26 01:30:18 UTC 2003


>Number:         54875
>Category:       ports
>Synopsis:       hpijs loops on fatal error
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 25 18:30:16 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Alan Batie
>Release:        FreeBSD 4.8-STABLE i386
>Organization:
RainDrop Laboratories
>Environment:
System: FreeBSD pyrex.batie.org 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat Apr 19 19:08:26 PDT 2003 root at pyrex.batie.org:/usr/src/freebsd/src/sys/compile/PYREX i386


	
>Description:
	I'm trying to get apsfilter to work with my HP DJ970 hooked up
	to a Win2K system.  It worked once, but after that once,
	hpijs 1.4.1 is complaining:

	    unable to write to output, fd=6, count=4096: m

	Which would be fine, clearly there's something I need to
	debug.  But it fails to exit, and goes into an infinite
	loop attempting to write and failing, until I kill it, and
	then apsfilter mails me a multi-hundreds of megabytes logfile
	(if I wait very long; it's syslogging them too).

	That 'm' at the end appears to be from the %m that's probably
	trying to print the errno error, but clearly isn't in the context
	where it will be interpreted.

>How-To-Repeat:
	Cause hpijs to fail writing output

>Fix:
	Personally, I think a write failure should cause it to abort right
	there, but I'll leave to the maintainers to decide how to handle
	it...

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list