From owner-freebsd-questions  Thu Nov 11  1:12:43 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 08B8C14CE5
	for <freebsd-questions@freebsd.org>; Thu, 11 Nov 1999 01:12:38 -0800 (PST)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1)
	id 11lqHM-000IKj-00; Thu, 11 Nov 1999 11:12:28 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Ryan Thompson <freebsd@sasknow.com>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: QPopper error message explanation? 
In-reply-to: Your message of "Wed, 10 Nov 1999 16:08:21 CST."
             <Pine.BSF.4.10.9911101549030.55051-100000@sasknow.com> 
Date: Thu, 11 Nov 1999 11:12:28 +0200
Message-ID: <70476.942311548@axl.noc.iafrica.com>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 10 Nov 1999 16:08:21 CST, Ryan Thompson wrote:

> .. popper[pid]: local.user@remote.host: -ERR SIGHUP or SIGPIPE flagged
> .. popper[pid]: local.user@remote.host: -ERR POP hangup
> 
> Does the above just signify that the user cancelled the check?  Or could
> this be a problem with my system?

It could be cancelled -- quite often the SIGPIPE's are indicative of
timed out connections, especially from clients that lost connectivity in
the middle of a session.

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message