Looks like a step in the right direction. How do I troubleshoot to figure out what application is appending/changing the value of PATH?
On Mon, May 20, 2013 at 2:56 AM, <[email protected]> wrote: > At Sat, 18 May 2013 18:34:47 -0500, > sindrome wrote: > > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning: > > Insecure world writable dir /tmp in PATH, mode 040777 > > At Sun, 19 May 2013 23:31:21 -0500, > sindrome wrote: > > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning: > > Insecure world writable dir /tmp/. in PATH, mode 041777 > > At Sun, 19 May 2013 21:30:03 +0200, > Simon Wright wrote: > > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:288: warning: > > Insecure world writable dir /tmp/ in PATH, mode 041777 > > /tmp > /tmp/. > /tmp/ > > Interesting three different messages. > It looks like three different entities adds their own value to your PATH. > > What you guys should do first is to find who sets stupid PATH for you. > I don't suppose portupgrade does. > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
