From owner-freebsd-ports@FreeBSD.ORG  Mon May 20 13:39:06 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 6D829169
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 13:39:06 +0000 (UTC)
 (envelope-from rde@tavi.co.uk)
Received: from kipling.tavi.co.uk (kipling.tavi.co.uk [81.187.145.130])
 by mx1.freebsd.org (Postfix) with ESMTP id 2A07E9AB
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 13:39:06 +0000 (UTC)
Received: from raksha.tavi.co.uk (raksha.tavi.co.uk [81.187.145.139])
 by kipling.tavi.co.uk (Postfix) with ESMTP id A830DC3F3E
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 14:38:53 +0100 (BST)
Date: Mon, 20 May 2013 14:38:53 +0100
From: Bob Eager <rde@tavi.co.uk>
To: freebsd-ports@freebsd.org
Subject: Re: Why does Samba requires 777 permissions on /tmp
Message-ID: <20130520143853.79242743@raksha.tavi.co.uk>
In-Reply-To: <CAFzAeSe4YTdUiqcxSDUGDf6fQEeDK_sDVYym1hsck8fms8kJqA@mail.gmail.com>
References: <CAFzAeSdgRotc34+eyfVHZBA-QGUCWJ1MZDYw1ysRxEV9MhG2BQ@mail.gmail.com>
 <8661yedqyy.wl%poyopoyo@puripuri.plala.or.jp>
 <CAFzAeSe4YTdUiqcxSDUGDf6fQEeDK_sDVYym1hsck8fms8kJqA@mail.gmail.com>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; i386-portbld-freebsd9.1)
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUwXjFLc0vD0cS7y7zw9PDZ4tkWSRaVrZZ+m39qi2tXfVj////7+/utwK4IPggAOAAJUUA7AAABKklEQVQ4jWPYjQMwDFYJp0NKEKCNJmEf9h8CsimXiL2e33s3/e7F7K2Cs3f3dCMkQkMKj4YuCY3K3iR+e7fMaiSjvkX0/5cFGrWpe2uLzOpaExUVqMS/8PX/Re5ey960OLBTZpFA8+IlSBKPQ92zNyUUBsosN58uIY0k8f+/ONCoYytkVuhWzVwNkYiYbqk5M3NmOVBi41YZ8RsGF7shEtFb5KJ3r969CyixM7OTPeFUxG2IxLO8/9/SvqXlc+/x3h295YzLlj2nIRJQj//nRvc5TEIal8RsXBLVuCQwIgoq/u80DomP6HEOk/iOS+IJLonZOCT+ReOQ+Lkbh0QKLonbOCR+7MYhsRqHBJrVcIl/1TgklqKLQyQ+tGKIgyQOqXpjig94diZRAgAXmDX6jyWafAAAAABJRU5ErkJggg======
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 13:39:06 -0000

On Mon, 20 May 2013 08:03:09 -0500
sindrome <sindrome@gmail.com> wrote:

> Looks like a step in the right direction.  How do I troubleshoot to
> figure out what application is appending/changing the value of PATH?

Nothing is. As far as I can see.

What I think is happening is that portupgrade is building and running
shell scripts in /tmp. It's running them with (in ruby):

  system('/tmp/script')             [roughly]

The ruby runtime is checking the *path-to-the-command* and THAT is what
it's complaining about.

Try setting PKG_TMPDIR (in pkgtools.conf) to some suitable non world
writable temporary directory.

I have an older ports tree on this machine or I'd try it myself. I had
to download the latest sources to check all this,