Date: Sun, 19 May 2013 15:14:35 -0400 From: Jerry <jerry@seibercom.net> To: freebsd-ports@freebsd.org Subject: Re: Why does Samba requires 777 permissions on /tmp Message-ID: <20130519151435.3a141585@scorpio> In-Reply-To: <CAFzAeSdhNp3zor_ofMS7P1We6Wgoa5fyxeFFDxq3tPkB2CgYyA@mail.gmail.com> References: <CAFzAeSdgRotc34%2BeyfVHZBA-QGUCWJ1MZDYw1ysRxEV9MhG2BQ@mail.gmail.com> <CADLo83-pFi8E-Wdoyju7YxBmOR67Qr4OWmZA-2x8_Um1F2bwoQ@mail.gmail.com> <CAFzAeSd%2B7oubgZ%2BzSJnmfNPA9v1=T41c=VF0C-sbz=vhyVE_OA@mail.gmail.com> <20130519115232.49f52d01@scorpio> <CADLo83-my3xBj9G9_dT0=FGfvK0jaRFQUhmk_YtRx3h8S_g2%2BQ@mail.gmail.com> <CAFzAeSdhNp3zor_ofMS7P1We6Wgoa5fyxeFFDxq3tPkB2CgYyA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 19 May 2013 13:34:49 -0500 sindrome articulated: > On Sun, May 19, 2013 at 11:48 AM, Chris Rees <utisoft@gmail.com> > wrote: > > > On 19 May 2013 16:52, "Jerry" <jerry@seibercom.net> wrote: > > > > > > On Sun, 19 May 2013 09:57:52 -0500 > > > sindrome articulated: > > > > > > > I checked everywhere (in .cshrc etc..) as well as "echo $PATH" > > > > and /tmp is not in there. I'm not sure where it's picking > > > > up /tmp in the path > > > > > > Same here. I have no idea where it is getting "tmp" from. At > > > least it doesn't appear to be causing any problems. > > > > Is that with portupgrade too? > > > Chris, > > I'm not sure I understand your question. Portupgrade barks about > the /tmp directory being world writable. I pasted the exact errors > earlier in this thread. I looked in my path and can't find /tmp in > there and can't figure how to get rid of ruby complaining unless I > remove the writable permissions. When I do that my windows desktop > can't authenticate to my samba server. There has to be a root of > this problem to make them both work. Is there some other place > portupgrade is having /tmp amended on without it being in my $PATH? If I am not mistaken, portupgrade only started with this BS about 6 months ago after it, itself was updated. It might be something hard coded by error into the program. I reported this once before to the port maintainer <bdrewery@FreeBSD.org>; however, I never received a response. Maybe I should file a PR against it. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130519151435.3a141585>