Subject: Re: Anyone see what's wrong with this trace?
To: Bill Stouder-Studenmund <wrstuden@NetBSD.org>
From: Steven M. Bellovin <firstname.lastname@example.org>
Date: 09/03/2007 20:13:53
On Mon, 3 Sep 2007 16:28:51 -0700
Bill Stouder-Studenmund <wrstuden@NetBSD.org> wrote:
> On Mon, Sep 03, 2007 at 01:05:56PM +0100, Matthias Scheler wrote:
> > On Sun, Sep 02, 2007 at 10:36:50PM -0700, Bill Stouder-Studenmund
> > wrote:
> > > Fetchmail dumps the following when this happens:
> > >
> > > fetchmail: connection to pop.coxmail.com:pop3 [126.96.36.199/110]
> > > failed: Interrupted system call.
> > > POP3 connection to pop.coxmail.com failed: Interrupted system call
> > > fetchmail: Query status=2 (SOCKET)
> > >
> > > Occasionally it works. I don't yet have a trace for when that's
> > > happening.
> > >
> > > Any thoughts?
> > Do you use "fetchmail -d <...>"? If you do can you try increasing
> > the value?
> Yes and no. I've seen this with fetchmail -d 180 and with it at the
> command line.
> Any idea what's wrong? How would delaying more help? I'm starting to
> think I may know, but I'd like to hear your thoughts. :-)
With a large mailbox in mbox format, it can take a long time to copy;
you can also run into locking issues. Also, were you on a slow link?
I've had problems that way, too.
--Steve Bellovin, http://www.cs.columbia.edu/~smb