> From [EMAIL PROTECTED] Thu Aug 17 19:43:54 2000
> Date: Thu, 17 Aug 2000 18:45:31 -0700 (PDT)
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: LPRng: IFHP runaway process
>
> > From [EMAIL PROTECTED] Thu Aug 17 11:30:15 2000
> > Date: Thu, 17 Aug 2000 13:28:02 -0400
> > From: "William R. Knox" <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: LPRng: IFHP runaway process
> >
> > I have a Phaser 850 set up to print over the AppSocket port with
> > IFHP-3.3.19 and LPRng-3.6.23. The printcap follows the current
> > recommendation of letting IFHP make the connection to the 9100 port (see
> > printcap entry below). However, it seems that IFHP can't handle a
> > connection flakeout (to use the technical term) as well as LPRng can. I
> > just had a print job suck up 25% of the CPU on an Sun Enterprise 250
> > server (well, the CPU time was available, but still...) as it tried to
> > reestablish the connection at a rate of once every millisecond or two.
> > Here is a slice of the relevant log entries:
>
> You can back this off to 500 milliseconds safely. I will put this into
> the next release.
>
> Sigh...
Get the latest beta of the ifhp filter and try this:
ftp://ftp.astart.com/pub/LPRng/private/ifhp-....
I THINK (no promises) that this might have the problem solved.
Please tell me if it does.
Patrick
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
