From owner-freebsd-current Sun Jan 2 17:40:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id A003015204 for ; Sun, 2 Jan 2000 17:40:17 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id CAA17589 for current@FreeBSD.org; Mon, 3 Jan 2000 02:40:14 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 881938863; Mon, 3 Jan 2000 02:02:44 +0100 (CET) Date: Mon, 3 Jan 2000 02:02:44 +0100 From: Ollivier Robert To: current@FreeBSD.org Subject: Re: several procmail jobs hang ... Message-ID: <20000103020244.A33752@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.org References: <20000102200003.A1618@titan.klemm.gtn.com> <20000102201039.A4336@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <20000102201039.A4336@titan.klemm.gtn.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Andreas Klemm: > procmail 3.14 bug, or does the new procmail version introduce > some new features in area where in -current is something wrong. > Not easy to say for me ... Check your locking settings on both versions. You may find that you're using different locking mechanisms... PS : and please, don't quote your own entire message, everybody including you has already seen it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message