From owner-freebsd-questions Sat Jan 23 08:39:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19212 for freebsd-questions-outgoing; Sat, 23 Jan 1999 08:39:50 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19200 for ; Sat, 23 Jan 1999 08:39:44 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.10 #1) id 10455r-000Bho-00; Sat, 23 Jan 1999 15:35:27 +0000 Date: Sat, 23 Jan 1999 15:35:27 +0000 From: Ben Smithurst To: SuperUser Cc: questions@FreeBSD.ORG Subject: Re: cucipop locking Message-ID: <19990123153527.A44970@scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SuperUser wrote: > The cucipop INSTALL file instructs the reader to edit the config.h file > to select appropriate locking methods. The config.h file says run the > lockingtest program part of the procmail installation process to test > which (locking) combinations make sense. Where is the lockingtest > program located? Is there some other way to select appropriate combinations. If you just install from the port (/usr/ports/mail/cucipop), then that should do the right thing. It appears from the port's patches that you should be enabling `USEdot_lock' and `USEflock'. I'd still recommend you use the port though. -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message