From owner-freebsd-ports@FreeBSD.ORG Mon May 16 18:11:34 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCDD716A4CE for ; Mon, 16 May 2005 18:11:34 +0000 (GMT) Received: from www235.sakura.ne.jp (www235.sakura.ne.jp [202.181.97.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4669F43D9F for ; Mon, 16 May 2005 18:11:34 +0000 (GMT) (envelope-from koma2@lovepeers.org) Received: from [192.168.11.5] (61-26-245-137.rev.home.ne.jp [61.26.245.137]) (authenticated bits=0) by www235.sakura.ne.jp (8.12.11/8.12.11) with ESMTP id j4GIB8br012991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 May 2005 03:11:13 +0900 (JST) (envelope-from koma2@lovepeers.org) Message-ID: <4288E23B.5070703@lovepeers.org> Date: Tue, 17 May 2005 03:11:07 +0900 From: KOMATSU Shinichiro User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20050515154745.T4991@office.cheeze.org> In-Reply-To: <20050515154745.T4991@office.cheeze.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jubal Kessler Subject: Re: portsdb -uU leaves lockfiles in /tmp X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2005 18:11:35 -0000 Hi, Jubal Kessler wrote: > I run 'portsdb -uU' every night. I've just noticed that lockfiles are > being left in /tmp after each invocation. The files look like: > > /tmp/courier-authlib.locktest.XXXX > > The Makefile in security/courier-authlib references $LOCKTEST, which makes > the above lockfile. I have two questions: > > 1. Why is portsdb doing this? Because "portsdb -u" invokes "make index" internally. That "make index" invokes "make describe" in security/courier-authlib-base, and the following line of security/courier-authlib/Makefile (included by courier-authlib-base) LOCKTEST!= ${MKTEMP} /tmp/courier-authlib.locktest.XXXXX is evaluated, and this "mktemp" creates tempfile in /tmp. So this is a problem of security/courier-authlib{,-base} ports themselves, rather than portupgrade. > 2. How can I make portsdb be as verbose as possible, and show me > what it's doing when it reaches the point where it creates the > lockfiles? I saw portsdb source, but no "verbose" option could be found.