Thanks for your reply Terrance, may I know if there are any solution for this please? I really have no idea where to start finding.
On Saturday, May 10, 2014 3:25:10 AM UTC+8, Terrance Shepherd wrote: > > This usually happens when ruby can not find a temp directory to write to > and so vagrant falls back to use the current directory. > > > On Fri, May 9, 2014 at 2:35 PM, Liew Jun Tung > <[email protected]<javascript:> > > wrote: > >> Hi all, I have been searching the internet for a few hours now and I >> can't find any solutions to this weird and annoying thing that's happening >> to my desktop. Whenever I issued a vagrant command ('vagrant init', >> 'vagrant up', or 'vagrant') via command prompt. It will produce all sorts >> of junk files with names like these: >> >> vagrant20140510-4308-1lud7je >> vagrant20140510-4308-1lud7je2 >> vagrant20140510-4308-1lud7je2.lock >> vagrant20140510-4308-r90ril >> vagrant20140510-4308-r90ril1 >> >> I have tried uninstalling all the plugins, install and update into new >> version of vagrant and virtualbox. Does anyone knows how to fix it? I am >> seriously out of idea here. >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
