Running your `rsync ...` command without sudo, I then successfully compiled my code.
Once I finished the above, I saw that you mentioned "root user copy the whole folder," I figured I should re-run the `rsync ...` but with "sudo" in front of the command. However, doing an ls -lrot on my VM shows that my /u01/build/share directory is owned by "kevin". That's a result of the following change that I added to my Vagrantfile: config.vm.synced_folder "c:/dev/share", "/u01/build/share", type: "rsync", owner: "kevin" When I tried to re-build on /u01/build/share/my_webapp with `mvn clean`, I still got an IO.Exception on a single file with the odd question marks (?) in the permissions section of the ls output. I'm using Windows for my host, so NFS isn't possible. Any other ideas? I appreciate your suggestions, Alvaro. On Tuesday, April 15, 2014 8:45:40 PM UTC-4, Alvaro Miranda Aguilera wrote: > > Hello, > > The way the shared folder is implemented,is not a real filesystem, so some > languages have problems with the code in there. I know python fail on some > operations, so maybe your is hitting that. > > The first troubleshooting you can do is a root user copy the whole folder > > rsync -PavzHl /source /test > > and try in test.. as root the permissions will remain the same and with > those parameters links will be copied as links, etc. > > If that works, blame virtualbox shared folder, and try to use vagrant to > rsync the files to the vm. > > If the copy also fails, then the issue is not on the filesystem, try to > do chown -R kevin: /test and try, if that work, then is permissions.. on > Vagrantfile you can setup owner and permissions of the shared folder. > > Give a try let's see where it fails/work.. > > Alvaro. > -- 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.
