Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Shared folder file timestamps not updating #707
I'm not sure if this is a Vagrant issue or a VirtualBox issue, but I thought I'd ask here first.
I'm running Vagrant on OSX Lion with the base lucid32 box. When I try to run guard within the VM, it works fine if I touch the files from within the VM. However, touching the files in OSX doesn't trigger any of the guards even though the file changes are successfully synced over. Any ideas?
I don't have any ideas, but definitely not a Vagrant issue itself, unless there is a setting I'm forgetting to set.
There has always been oddities with guard and virtualbox shared folders so I'm not sure :( I'd try pinging the [vagrant] mailing list to see if anyone else has seen this.
If you find any more evidence to think this is a Vagrant issue, please let me know and I'll reopen.
Since VirtualBox doesn't support symlinks from Windows host shared folder to Linux, it makes it useless for Node.js projects (npm requires symlinks). My solution was to watch for file changes using inotifywait and run rsync to another folder where the node modules are installed. Unfortunately, inotifywait doesn't see any changes when I make them from windows. Any other ideas on this one, guys?
UPDATE: I just saw the ticket on virtual box and it says I need to update guest additions as well, which I did not. Did you guys update your guest editions?
UPDATE: I updated guest additions and no luck. Same issue...
referenced this issue
Jun 1, 2012
I'm using an Ubuntu 12.04 box I packaged with the updated Guest Additions (you can grab it @ http://public.g0dly.com/boxes/precise64-4.1.18.box). You just run vagrant on the guest OS with
Let me know if you have any more questions
Well I'm running Arch Linux Virtual Box guest in a Windows 8 host. I have:
installed but I still don't get the OS updates on file changes from my shared (samba) drives. My shared drive has symlinks enabled via the
Am I missing something out? Also @clintberry virtualbox supports symlinks but it's tricky: