hi,

I'm using IFHP 3.4.4, it works very nice but sometimes it goes into a
loop and consumes about 80% of the cpu power:

it happens exclusively with the HP8000 and 8150 series (and very rarely
with the 4050), this is what lpq shows then:

 Filter_status: starting transfer at 12:07:42.540
 Filter_status: initial job type 'POSTSCRIPT' at 12:07:42.540
 Filter_status: decoded job type 'POSTSCRIPT' at 12:07:42.541
 Filter_status: job type 'POSTSCRIPT' at 12:07:42.541
 Filter_status: transferring 558007 bytes at 12:07:42.542
 Filter_status: 25 percent done at 12:07:43.773
 Filter_status: 51 percent done at 12:07:44.268
 Filter_status: 77 percent done at 12:07:49.572
 Filter_status: data sent at 12:07:55.350
 Filter_status: sent job file at 12:07:55.351
 Filter_status: getting end using 'pjl job/eoj' at 12:07:55.352
 Filter_status: no end response from printer, timeout 0 at 12:10:57.697
 Filter_status: (of) OF process running at 12:10:57.700
 Rank   Owner/ID                  Class Job Files                 Size
Time
active kappen@HASY227K+464          A   464 http://journals.iuc 558007 1

sometimes it also says 'connection reset by peer'


The jet direct interface at that time is ok and ready to print, but the
IFHP filter is looping, truss shows:

alarm(0)                                        = 0
sigaction(SIGALRM, 0xFFBEEEE8, 0xFFBEEF68)      = 0
sigprocmask(SIG_UNBLOCK, 0xFFBEEF98, 0xFFBEF00C) = 0
read(1, 0xFFBEF0E0, 1023)                       = 0
sigaction(SIGALRM, 0xFFBEEF58, 0xFFBEEFD8)      = 0
alarm(0)                                        = 0
fcntl(1, F_GETFL, 0x00000000)                   = 130
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF008, 0) = 0
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF00C, 0) = 0
setsockopt(1, 65535, 8192, 0xFFBEF010, 4, 0)    = 0
fcntl(1, F_SETFL, 0x00000002)                   = 0
poll(0xFFBEF4B8, 1, -1)                         = 1
fcntl(1, F_GETFL, 0x00000000)                   = 2
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF008, 0) = 0
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF00C, 0) = 0
setsockopt(1, 65535, 8192, 0xFFBEF010, 4, 0)    = 0
fcntl(1, F_SETFL, 0x00000082)                   = 0
getcontext(0xFFBEEEB8)
alarm(0)                                        = 0
sigaction(SIGALRM, 0xFFBEEEE8, 0xFFBEEF68)      = 0
sigprocmask(SIG_UNBLOCK, 0xFFBEEF98, 0xFFBEF00C) = 0
read(1, 0xFFBEF0E0, 1023)                       = 0
sigaction(SIGALRM, 0xFFBEEF58, 0xFFBEEFD8)      = 0
alarm(0)                                        = 0
fcntl(1, F_GETFL, 0x00000000)                   = 130
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF008, 0) = 0
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF00C, 0) = 0
setsockopt(1, 65535, 8192, 0xFFBEF010, 4, 0)    = 0
fcntl(1, F_SETFL, 0x00000002)                   = 0
poll(0xFFBEF4B8, 1, -1)                         = 1
fcntl(1, F_GETFL, 0x00000000)                   = 2
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF008, 0) = 0
fstat64(1, 0xFFBEEF10)                          = 0
getsockopt(1, 65535, 8192, 0xFFBEF010, 0xFFBEF00C, 0) = 0
setsockopt(1, 65535, 8192, 0xFFBEF010, 4, 0)    = 0


I know that the implementation of these networkinterfaces is completely
crappy, because they tend also to not wake up from the powersave mode
etc. Though it would be nice to prevent IFHP from looping in those
situations because it kind of blocks the printer...

any ideas (?)

regards
                ~christoph


-- 
/*   Christoph Beyer     |   Office: Building 2b / 23     *\ 
 *   DESY                |    Phone: 040-8998-2317        *
 *   - IT -              |      Fax: 040-8994-2317        *
\*   22603 Hamburg       |     http://www.desy.de         */

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

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.
-----------------------------------------------------------------------------

Reply via email to