Re: [vagrant-up] detritus in /tmp

2016-06-29 Thread Alvaro Miranda Aguilera 
any chance you can update ?

i think 1.8.4 is our

On Mon, Jun 27, 2016 at 12:39 PM, Bill Houle  wrote:

> $ vagrant -v
> Vagrant 1.8.1
> $ vagrant plugin list
> vagrant-share (1.1.5, system)
>
> And with those 2 commands, 10 more temporary files in /tmp...
>
> (Vagrant installed from RPM of Vagrant site.)
>
>
> On Saturday, June 18, 2016 at 11:48:09 AM UTC-7, Alvaro Miranda Aguilera
> wrote:
>>
>> whats the output of vagrant version and vagrant plugin list ?
>>
>> Thanks
>> Alvaro
>>
>> On Wed, Jun 8, 2016 at 7:47 PM, Bill Houle  wrote:
>>
>>> I'm on CentOS 6.8 with Vagrant 1.8.1 and VirtualBox 5.0.20 provider.
>>>
>>> When I run "vagrant foo" (an invalid command), I get 4 "vagrant"
>>> files created in /tmp, plus a "d" directory with a config file within.
>>> When I run "vagrant -v" (a relatively inactive command), I get more of
>>> the same.
>>> When I run "vagrant up", yup, you guessed it.
>>>
>>> The cruft tends to build up quickly. Why? Especially for invalid or
>>> non-VM'ish commands?!? Is there any rule for when they are safe to purge?
>>>
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Vagrant" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to vagrant-up+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/vagrant-up/caef6192-5b92-4d07-8189-859a27a5e376%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/70ed32bf-7139-4fac-a757-161c50abfb0d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyww0Qyv8AU71Tsk%2BfxBag8YTmN3tgioP%3D5cBdcGMfNgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] detritus in /tmp

2016-06-27 Thread Bill Houle 
$ vagrant -v
Vagrant 1.8.1
$ vagrant plugin list
vagrant-share (1.1.5, system)

And with those 2 commands, 10 more temporary files in /tmp...

(Vagrant installed from RPM of Vagrant site.)


On Saturday, June 18, 2016 at 11:48:09 AM UTC-7, Alvaro Miranda Aguilera 
wrote:
>
> whats the output of vagrant version and vagrant plugin list ?
>
> Thanks
> Alvaro
>
> On Wed, Jun 8, 2016 at 7:47 PM, Bill Houle  > wrote:
>
>> I'm on CentOS 6.8 with Vagrant 1.8.1 and VirtualBox 5.0.20 provider.
>>
>> When I run "vagrant foo" (an invalid command), I get 4 "vagrant" 
>> files created in /tmp, plus a "d" directory with a config file within.
>> When I run "vagrant -v" (a relatively inactive command), I get more of 
>> the same.
>> When I run "vagrant up", yup, you guessed it.
>>
>> The cruft tends to build up quickly. Why? Especially for invalid or 
>> non-VM'ish commands?!? Is there any rule for when they are safe to purge?
>>
>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to vagrant-up+...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/caef6192-5b92-4d07-8189-859a27a5e376%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/70ed32bf-7139-4fac-a757-161c50abfb0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] detritus in /tmp

2016-06-18 Thread Alvaro Miranda Aguilera 
whats the output of vagrant version and vagrant plugin list ?

Thanks
Alvaro

On Wed, Jun 8, 2016 at 7:47 PM, Bill Houle  wrote:

> I'm on CentOS 6.8 with Vagrant 1.8.1 and VirtualBox 5.0.20 provider.
>
> When I run "vagrant foo" (an invalid command), I get 4 "vagrant"
> files created in /tmp, plus a "d" directory with a config file within.
> When I run "vagrant -v" (a relatively inactive command), I get more of the
> same.
> When I run "vagrant up", yup, you guessed it.
>
> The cruft tends to build up quickly. Why? Especially for invalid or
> non-VM'ish commands?!? Is there any rule for when they are safe to purge?
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/caef6192-5b92-4d07-8189-859a27a5e376%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ex9baWueMeKAxfpcG5dkkRGorBu906SgMtxGiw6FXck8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] detritus in /tmp

2016-06-08 Thread Bill Houle 
I'm on CentOS 6.8 with Vagrant 1.8.1 and VirtualBox 5.0.20 provider.

When I run "vagrant foo" (an invalid command), I get 4 "vagrant" 
files created in /tmp, plus a "d" directory with a config file within.
When I run "vagrant -v" (a relatively inactive command), I get more of the 
same.
When I run "vagrant up", yup, you guessed it.

The cruft tends to build up quickly. Why? Especially for invalid or 
non-VM'ish commands?!? Is there any rule for when they are safe to purge?


-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/caef6192-5b92-4d07-8189-859a27a5e376%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.