From owner-freebsd-questions Thu Nov 4 8: 8: 7 1999 Delivered-To: freebsd-questions@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 9C2E21504C for ; Thu, 4 Nov 1999 08:07:55 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15]) by forrie.net (8.9.3/8.9.3) with ESMTP id LAA26641 for ; Thu, 4 Nov 1999 11:07:13 -0500 (EST) Message-Id: <4.2.1.19991104110234.00a7c8a0@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 Date: Thu, 04 Nov 1999 11:04:18 -0500 To: freebsd-questions@freebsd.org From: Forrest Aldrich Subject: popper getting stuck Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been experiencing this problem for some time with qpopper on FreeBSD-2.2.8. This applies to past versions of qpopper and the latest 3.0b20. What happens is, intermittently, there will be several popper processes spawned, that appear to be stuck in "lockf" state. I have to killall them, HUP sendmail and it works for a short time, but it happens again. I've recompiled sendmail and popper against the latest libs. I recompiled popper with --enable-servermode to see if that would work. No go. This is a complete mystery, and I wonder if anyone else has seen this problem. Thanks, _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message