Date: Tue, 17 May 2005 03:11:07 +0900 From: KOMATSU Shinichiro <koma2@lovepeers.org> To: freebsd-ports@freebsd.org Cc: Jubal Kessler <jubal+freebsdports+20050515@cheeze.org> Subject: Re: portsdb -uU leaves lockfiles in /tmp Message-ID: <4288E23B.5070703@lovepeers.org> In-Reply-To: <20050515154745.T4991@office.cheeze.org> References: <20050515154745.T4991@office.cheeze.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4288E23B.5070703>