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%2BeyfVHZBA-QGUCWJ1MZDYw1ysRxEV9MhG2BQ@mail.gmail.com> <8661yedqyy.wl%poyopoyo@puripuri.plala.or.jp> <CAFzAeSe4YTdUiqcxSDUGDf6fQEeDK_sDVYym1hsck8fms8kJqA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130520143853.79242743>