From owner-freebsd-stable Mon Oct 5 10:25:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16232 for freebsd-stable-outgoing; Mon, 5 Oct 1998 10:25:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16197 for ; Mon, 5 Oct 1998 10:24:58 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.1/8.9.1) with ESMTP id KAA06116 for ; Mon, 5 Oct 1998 10:24:33 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Mon, 5 Oct 1998 10:24:33 -0700 (PDT) From: "Eric J. Schwertfeger" To: stable@FreeBSD.ORG Subject: has anyone been able to make maildrop work with a recent 2.2-SNAP? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had maildrop (same idea as procmail, but more flexible) working on a 2.2.7-RELEASE box, which I then upgraded to 2.2.7-19980828-SNAP. Now, when I try to run maildrop, it sits there for about 5 minutes and exits with the message "maildrop: Timeout quota exceeded." It's in C++ and I haven't had the time to trace out where it's having the problem, but I suspect that it's some subtle problem with file locking, either a bug in maildrop that didn't trigger with -RELEASE, or an actual change in semantics in -STABLE. http://www.geocities.com/SiliconValley/Peaks/5799/maildrop.README.html compiled without dotlocking. I also tried 2.2.7-19981004-SNAP with no improvement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message