Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Dec 1999 08:50:02 -0800 (PST)
From:      Juergen Lock <nox@jelal.kn-bremen.de>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/15532: Reboot just to kill a print job?
Message-ID:  <199912181650.IAA22168@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/15532; it has been noted by GNATS.

From: Juergen Lock <nox@jelal.kn-bremen.de>
To: Alexander Langer <alex@big.endian.de>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/15532: Reboot just to kill a print job?
Date: Sat, 18 Dec 1999 17:31:38 +0100

 On Sat, Dec 18, 1999 at 11:06:09AM +0100, Alexander Langer wrote:
 > Also sprach Juergen Lock (nox@jelal.kn-bremen.de):
 > 
 > > 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...
 > 
 > Yes, that happens to me every time I get those problems.
 
 Sounds like you get paper jam often?  (What printer is that?)
 
 > Also try booting the machine while the printer prints. The same
 > result.
 > 
  Oh.  even if you reset the printer too?
 
 > If you reboot your Windows box while the printer prints, the print-job
 > is completed at exactly this page where it stopped next boot.
 
  Whow :)  sounds like one thing that M$ did get right.
 (Well of course a unix box isn't supposed to be rebooted as often
 as you need to reboot a crashed wintendo box...  Or like, `The
 mouse cursor has moved.  Please reboot for the change to take
 effect.')
 > 
 > > 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?)
 > 
 > I usually use a combination of
 > lpc down all
 > lpc disable all
 > killall lpd
 > 
 > switch of the printer
 > restart lpd
 > 
 > switch on the printer
 > lpc up all
 > lpc enable all
 > 
 > Soemthink _like_ this usually fixes it.
 
  Hmm.  Does that also help when the filter still hangs blocking on
 the printer device like in my case, with no signal being able to
 kill it?  Somehow i doubt it...
 
  Regards,
 -- 
 Juergen Lock <nox.foo@jelal.kn-bremen.de>
 (remove dot foo from address to reply)
 


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912181650.IAA22168>