Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!styx!ames!ucbcad!ucbvax!H.CS.CMU.EDU!Rudy.Nedved From: Rudy.Nedved@H.CS.CMU.EDU Newsgroups: mod.computers.laser-printers Subject: Re: Transcript v2.0 bug Message-ID: <1986.11.20.23.25.14.Rudy.Nedved@h.cs.cmu.edu> Date: Thu, 20-Nov-86 18:41:43 EST Article-I.D.: h.1986.11.20.23.25.14.Rudy.Nedved Posted: Thu Nov 20 18:41:43 1986 Date-Received: Mon, 24-Nov-86 21:58:23 EST References: <8611202158.AA21420@weyl.Berkeley.EDU> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 50 Approved: laser-lovers@washington.arpa Rusty, The "correct" fix which worked for over a week was to simply commented out or delete the longjmp(), setjmp() and remove the spin loop on revdone with the pause in it. The code looks like the following: /* do page reversal if specified */ if (reversing = ((reverse != NULL) && canReverse)) { debugp((stderr,"reversing\n")); #ifndef CMUCS VOIDC setjmp(waitonreverse); if (!revdone) { VOIDC signal(SIGEMT, reverseready); #endif CMUCS if (pipe (fdpipe)) pexit2(prog, "reverse pipe", THROW_AWAY); . . . #ifndef CMUCS while (TRUE) { if (revdone) break; pause(); } } VOIDC signal(SIGEMT, SIG_IGN); #endif CMUCS debugp((stderr,"%s: reverse feeding\n",prog)); } I commented out the signal in psrv and the longjmp in reverseready(). I was not looking for a truly clean fix.... I received some changes today from Andy Shore but because I don't understand the legalities of purchased software...I will not send the changes. I saw a comment that ron@nprdc had this problem and a fix....this seems to be the fix Andy Shore picked up. As for the "errsXXXXX" file (where XXXXXX is the lpd pid also found in the lock file), they are created by the 4.3BSD version of lpd for the input filter. When the input filter terminates, lpd copies the file onto the end of the logfile if it exists....and deletes the file. If you cancel a print request getting processed, many times the errsXXXX file will be left around. I have a community of 3000 or so people using about 14 LaserWriters+ and two LinoType 300s directly, by Scribe, MacDraw or by TeX. One of the failure modes seems to be a spinloop for the PostScript machine....jobtimeout or whatever does not seem to be kicking it. Yet a power cycle of the printer does the job. Cheers, -Rudy