Subject: Re: fetchmail hang, dud read error?
To: Andrew Cagney <firstname.lastname@example.org>
From: Thor Lancelot Simon <email@example.com>
Date: 08/15/2002 13:05:44
On Thu, Aug 15, 2002 at 12:41:23PM -0400, Andrew Cagney wrote:
> >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.
Are you using "kdump -e <emulationname>" for whatever the correct emulation
is? I'm not sure it automatically selects correctly.