Why does Samba requires 777 permissions on /tmp

[sindrome]

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?



On Sun, May 19, 2013 at 11:48 AM, Chris Rees <utisoft at gmail.com> wrote:

> On 19 May 2013 16:52, "Jerry" <jerry at 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
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>