Chris,
That did it! Thanks so much for the help. Just in case if anyone else is
reading this long thread, you cannot have a colon period (:.) at the end of
your pathmeaning do not include the current directory as part of the
$path
On Mon, May 27, 2013 at 3:54 PM, Chris Rees wrote:
>
> O
On 27 May 2013 20:45, "sindrome" wrote:
>
> Hi Guys,
>
> I just got home from being out of town and the problem still persists even
> after I removed . from my path.
>
> echo $PATH
>
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/home/sindrome/.gnupg:/home/sindrome/bin:/hom
Hi Bob,
I just went into /usr/local/etc/pkgtools.conf and changed the PKG_TMPDIR
variable to a non-world writable directory called /build and still see the
warnings below:
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
Insecure world writable dir /tmp/ in PATH, mode 041777
/
Did you try changing PKG_TMPDIR as I suggested? (see below)
On Mon, 27 May 2013 14:45:05 -0500
sindrome wrote:
> Hi Guys,
>
> I just got home from being out of town and the problem still persists
> even after I removed . from my path.
>
> echo $PATH
> /bin:/usr/lib:/sbin:/usr/bin:/usr/local/s
Hi Guys,
I just got home from being out of town and the problem still persists even
after I removed . from my path.
echo $PATH
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome
On 20/05/2013 15:38, Bob Eager wrote:
On Mon, 20 May 2013 08:03:09 -0500
sindrome wrote:
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 t
Please let us know if it's still a problem and we can narrow it down
further. :)
Chris
On 20 May 2013 20:20, "sindrome" wrote:
> Apologies Chris. I removed it but am out of town so will have to test
> next week. I appreciate all your help. I'll let you know if that makes it
> go away.
>
>
> O
Apologies Chris. I removed it but am out of town so will have to test next
week. I appreciate all your help. I'll let you know if that makes it go
away.
On Mon, May 20, 2013 at 1:04 PM, Chris Rees wrote:
> You are not 'sure'.
>
> Please do not solicit help and claim that you know better-- I
You are not 'sure'.
Please do not solicit help and claim that you know better-- I told you
hours ago to remove . from your path.
Chris
On 20 May 2013 17:49, sindrome wrote:
> Fair enough but that's not the root of this problem I'm sure
>
>
> On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen w
Ok, I've discovered a combination of things that will reproduce that message,
and it REALLY does come down to NOT HAVING '.' IN YOUR PATH, especially for
user root.
If I don't have '.' in my path, I can "cd" to any directory and Ruby will not
complain when I run the system() command (or the equiv
Fair enough but that's not the root of this problem I'm sure
On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen wrote:
> On Mon, May 20, 2013 at 6:45 PM, sindrome wrote:
> > Clearly I'm not the only one with this problem. Something is amending
> onto
> > the PATH and I'd like to get to the bo
On Mon, May 20, 2013 at 6:45 PM, sindrome wrote:
> Clearly I'm not the only one with this problem. Something is amending onto
> the PATH and I'd like to get to the bottom of this. I'm sure it will help a
> lot of people.
Well, start by taking the current directory ('.') out of your PATH.
(It is
Clearly I'm not the only one with this problem. Something is amending onto
the PATH and I'd like to get to the bottom of this. I'm sure it will help
a lot of people.
On Mon, May 20, 2013 at 11:39 AM, Torfinn Ingolfsen wrote:
> On Mon, May 20, 2013 at 7:20 AM, Erich Dollansky
> wrote:
> >
> >
On Mon, May 20, 2013 at 7:20 AM, Erich Dollansky
wrote:
>
> Could it be that we all got this message but did not bother because we
> get so many warnings during an upgrade?
Nope. FWIW, portupgrade works without errors here.
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE
I modified the PATH to remove those items you mentioned but I'm still
getting the following when I portupgrade. How can I track down what is
amending /tmp onto the PATH?
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:1170: warning:
Insecure world writable dir /tmp/. in PATH, mode 041777
/
On 20 May 2013 17:07, "sindrome" wrote:
>
> Some are just document directories in my home. Do you have a suggested
PATH that I can use
Default PATH is good, from /etc/profile.
Adding ~/bin won't hurt, if you like that.
Chris
> On Mon, May 20, 2013 at 11:02 AM, Chris Rees wrote:
>>
>>
>> On 20
Some are just document directories in my home. Do you have a suggested PATH
that I can use
On Mon, May 20, 2013 at 11:02 AM, Chris Rees wrote:
>
> On 20 May 2013 16:53, "sindrome" wrote:
> >
> > echo $PATH
> >
> /bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/local/l
On 20 May 2013 16:53, "sindrome" wrote:
>
> echo $PATH
>
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/local/lib32/compat:/usr/X11R6/bin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome/docs/config:/sbin:/bin:/etc:/us
echo $PATH
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/local/lib32/compat:/usr/X11R6/bin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome/docs/config:/sbin:/bin:/etc:/usr/local/etc::/usr/bin:/usr/games:/usr/local/sbi
Hi,
On Mon, 20 May 2013 14:38:53 +0100
Bob Eager wrote:
> On Mon, 20 May 2013 08:03:09 -0500
> sindrome 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
Just out of curiosity, what is your PATH set to in whatever console/terminal
window before you run portupgrade ( echo $PATH )?
On Mon, May 20, 2013 at 08:03:09AM -0500, sindrome wrote:
> Looks like a step in the right direction. How do I troubleshoot to figure
> out what application is appending/
On Mon, 20 May 2013 08:03:09 -0500
sindrome 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
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, wrote:
> At Sat, 18 May 2013 18:34:47 -0500,
> sindrome wrote:
> > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483
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: warni
Hi,
On Sun, 19 May 2013 23:31:21 -0500
sindrome wrote:
> You can see the sticky bit is indeed set and I'm still getting these
> errors:
>
you must first realise that this is not an error but a warning
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> Insecure world writa
You can see the sticky bit is indeed set and I'm still getting these errors:
stat -r /tmp
90 7418880 041777 3 0 0 29641368 512 1368950908 1369024120 1369024120
1130953852 16384 4 0 /tmp
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
Insecure world writable dir /tmp/. in PAT
On Sun, 19 May 2013 15:59:12 -0500
Jimmy wrote:
> From the original post that started this thread, I noticed that the
> error from portupgrade/ruby was showing the permissions that it didn't
> like as mode 040777 (octal). This is definitely with the sticky bit
> turned OFF. It should be 041777.
From the original post that started this thread, I noticed that the
error from portupgrade/ruby was showing the permissions that it didn't
like as mode 040777 (octal). This is definitely with the sticky bit turned
OFF.
It should be 041777. 'stat -r /tmp' will print the permissions in octal rath
On Sun, 19 May 2013 21:30:03 +0200
Simon Wright wrote:
> On 05/19/13 20:56, Bob Eager wrote:
> > On Sun, 19 May 2013 13:34:49 -0500
> > sindrome wrote:
> >
> >> 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
On Sun, 19 May 2013 21:30:03 +0200
Simon Wright articulated:
> On 05/19/13 20:56, Bob Eager wrote:
> > On Sun, 19 May 2013 13:34:49 -0500
> > sindrome wrote:
> >
> >> 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 p
I concur with Simon. That's exactly when it started for me.
On May 19, 2013, at 2:30 PM, Simon Wright wrote:
> On 05/19/13 20:56, Bob Eager wrote:
>> On Sun, 19 May 2013 13:34:49 -0500
>> sindrome wrote:
>>
>>> can't authenticate to my samba server. There has to be a root of
>>> this problem
On 05/19/13 20:56, Bob Eager wrote:
On Sun, 19 May 2013 13:34:49 -0500
sindrome wrote:
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?
I went
Jerry is right. I have it set to 1777 too and still receive the error
On Sun, May 19, 2013 at 2:17 PM, Jerry wrote:
> On Sun, 19 May 2013 19:56:39 +0100
> Bob Eager articulated:
>
> > On Sun, 19 May 2013 13:34:49 -0500
> > sindrome wrote:
> >
> > > I'm not sure I understand your question. Por
On Sun, 19 May 2013 19:56:39 +0100
Bob Eager articulated:
> On Sun, 19 May 2013 13:34:49 -0500
> sindrome wrote:
>
> > 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
On Sun, 19 May 2013 13:34:49 -0500
sindrome articulated:
> On Sun, May 19, 2013 at 11:48 AM, Chris Rees
> wrote:
>
> > On 19 May 2013 16:52, "Jerry" wrote:
> > >
> > > On Sun, 19 May 2013 09:57:52 -0500
> > > sindrome articulated:
> > >
> > > > I checked everywhere (in .cshrc etc..) as well as
On Sun, 19 May 2013 13:34:49 -0500
sindrome wrote:
> 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
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
per
On 19 May 2013 16:52, "Jerry" 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
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 c
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
On Sun, May 19, 2013 at 2:36 AM, Chris Rees wrote:
>
> On 19 May 2013 00:34, "sindrome" wrote:
> >
> > I just found myself troubleshooting an issue wher
On 19 May 2013 00:34, "sindrome" wrote:
>
> I just found myself troubleshooting an issue where my desktop machine
> couldn't login to my local samba server unless I have the /tmp directory
> permissions set to 777. I'd like to have it 775 not only for security
> reasons but also because portupgra
On Sat, 18 May 2013 19:52:19 -0500
sindrome wrote:
> Thanks for that tip. I was hoping that was the root of it but upon
> looking at my path, I don't have /tmp in there. II used to have the
> sticky bit set on there. I just re-set it but portupgrade still keeps
> barking because it's world writ
Hi,
On Sun, 19 May 2013 07:06:46 +0100
Matthew Seaman wrote:
> On 19/05/2013 03:56, Erich Dollansky wrote:
> > Your problem must be caused by something else. At least, I cannot
> > remember to ever have seen /tmp with a different setting than 0777.
>
> I hope you mean 1777 (drwxrwxrwt) there.
On 19/05/2013 03:56, Erich Dollansky wrote:
> Your problem must be caused by something else. At least, I cannot
> remember to ever have seen /tmp with a different setting than 0777.
I hope you mean 1777 (drwxrwxrwt) there. That sticky bit is important.
Without it there are a number of nasty atta
Hi,
On Sat, 18 May 2013 19:52:19 -0500
sindrome wrote:
> Thanks for that tip. I was hoping that was the root of it but upon
> looking at my path, I don't have /tmp in there. II used to have the
> sticky bit set on there. I just re-set it but portupgrade still keeps
> barking because it's world
Thanks for that tip. I was hoping that was the root of it but upon looking
at my path, I don't have /tmp in there. II used to have the sticky bit set
on there. I just re-set it but portupgrade still keeps barking because it's
world writable. It seems that the conflict is Samba needs it to be wor
On Sat, 18 May 2013 18:34:47 -0500
sindrome wrote:
> I just found myself troubleshooting an issue where my desktop machine
> couldn't login to my local samba server unless I have the /tmp
> directory permissions set to 777. I'd like to have it 775 not only
> for security reasons but also because
47 matches
Mail list logo
