Subject: Re: fetchmail hang, dud read error?
To: Jaromir Dolecek <email@example.com>
From: Andrew Cagney <firstname.lastname@example.org>
Date: 08/15/2002 12:41:23
> Andrew Cagney wrote:
>> > 8983 fetchmail RET read 24/0x18
>> > 8983 fetchmail CALL read(0x3,0x18af000,0x5)
>> I think the errno -3 is due to the cntrl-c.
> -3 is ERESTART. It's kernel internal thing, the errno is never actually
> delivered to userland, it just appears in ktrace.
> Don't you happen to have "old" (like more than 6 months) kdump?
> kdump contains special code for such ktrace records, and it should
> print 'RET read RESTART', rather than 'read -1 errno -3 ...'.
> The internal EJUSTRETURN/ERESTART codes changed recently, that's
> why kdump should be uptodate to catch this properly.
It's what ever is at the head of the 1.5 branch.
> In other words: fetchmail hangs in read(), waiting for some incoming
> data to arrive. The stuff after PSIG SIGINT appears to be executed
> by signal handler (terminate_run() of fetchmail?).
Anyway, fetchmail is trying to read:
A0007 OK Completed\r\n
but is getting
A0007 OK Completed\r\0
out of SSL. Is it a local or remote problem, I don't know.