Bug 69290 - magicfilter not re-entrant?
magicfilter not re-entrant?
Product: Red Hat Linux
Classification: Retired
Component: printconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-07-19 22:41 EDT by rdt
Modified: 2007-04-18 12:44 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-10 10:40:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description rdt 2002-07-19 22:41:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-3 i586)

Description of problem:
Multiple dvips | lpr  jobs that overlap seem to hang arbitrarily,
requiring lpc> kill to restart lpd.  If I separate the print jobs so that I
don't dvips a file until the previous run of mf_filter has terminated, they
print perfectly.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. dvips a1.dvi; dvips a2.dvi; dvips a3.dvi; ...

Actual Results:  Printing system hangs after two or three jobs print, 
requiring lpc> kill to restart it.

Expected Results:  Printing of a1.ps, a2.ps, a3.ps, ...

Additional info:

The files print normally if the dvips steps are done separately,
instead of in rapid succession.
Comment 1 Tim Waugh 2002-07-22 16:51:26 EDT
I have had several reports of similar behaviour to this, but haven't yet been 
able to track it down.  Any help would be appreciated!
Comment 2 rdt 2002-07-22 19:47:34 EDT
This might be a clue:  if I save dvips output as Postscript files, and do
lpr a1.ps; lpr a2.ps; ... , I don't seem to get the problem (two tests only).
So maybe it's interference between dvips and the printing system.
Comment 3 Tim Waugh 2004-12-10 10:40:50 EST
No longer use magicfilter.

Note You need to log in before you can comment on or make changes to this bug.