From owner-freebsd-bugs  Fri Dec 17 11:50: 7 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id C10E31577E
	for <freebsd-bugs@FreeBSD.org>; Fri, 17 Dec 1999 11:50:03 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id LAA80000;
	Fri, 17 Dec 1999 11:50:03 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254])
	by hub.freebsd.org (Postfix) with ESMTP id 77C5A14DD0
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 17 Dec 1999 11:46:04 -0800 (PST)
	(envelope-from nox@saturn.kn-bremen.de)
Received: from saturn.kn-bremen.de (uucp@localhost)
	by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id UAA01904
	for FreeBSD-gnats-submit@freebsd.org; Fri, 17 Dec 1999 20:43:08 +0100
Received: (from nox@localhost)
	by saturn.kn-bremen.de (8.9.3/8.8.5) id UAA25488;
	Fri, 17 Dec 1999 20:27:46 +0100 (CET)
Message-Id: <199912171927.UAA25488@saturn.kn-bremen.de>
Date: Fri, 17 Dec 1999 20:27:46 +0100 (CET)
From: Juergen Lock <nox@jelal.kn-bremen.de>
Reply-To: nox@jelal.kn-bremen.de
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/15532: Reboot just to kill a print job?
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         15532
>Category:       kern
>Synopsis:       Reboot just to kill a print job?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 17 11:50:02 PST 1999
>Closed-Date:
>Last-Modified:
>Originator:     Juergen Lock
>Release:        FreeBSD 3.3-STABLE i386
>Organization:
me?  organized?
>Environment:

	3.3-STABLE i386 and an (old) parallel printer

>Description:

	I just lpr'd a page and then heared strange sounds from
the printer:  paper jam...  Now i cannot remember when this printer
last had a paper jam in all the years i have it (if ever, it is
_old_, ink jet printers weren't even invented when i got it i
believe), but one day it had to happen i guess...  Anyway i hit
offline, teared off the offending page (i said the printer is
old :), killed the job and powecycled the printer (there's no other
way to reset it i believe), but when i then sent the job again the
printer only got garbage.  so i had to hit offline again...

	Well turned out the filter processes (gs...) from the jammed
job were still around, and i couldn't kill them either because they
were hanging on the (now offline again) printer device.  So the
only fix seemed to be a reboot. :/  (Or is there some way for a
device on the parallel port to indicate a reset/poweroff that this
printer just doesn't use?)

>How-To-Repeat:

	Switch offline and reset printer and kill the job when the
filter isn't yet finished sending data?

>Fix:
	
	??  Maybe add a `wakeup everyone waiting and flush and
ignore all output until close' ioctl to the lpt driver that lprm
could use when killing an active job?

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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message