Locking problems with ssh

[gucki]

When I try to start two ssh sessions to a running machine at the (almost) same timeI very often get an error in the second terminal like:

An action 'fetch_ip' was attempted on the machine 'xxx',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.

I did not have this error when using vagrant with virtualbox. I wonder if locking is really necessary for vagrant ssh? If it is necessary, probably a --waitflag would be nice, which should make the command to not fail but wait for a previous lock to be released.

To reproduce just open two terminals and paste vagrant ssh. It should show the error above in the second terminal.

[fgrehm]

This is likely to be fixed with GH-318 :)

[fgrehm]

It wasn't fixed with 318 but I worked around the issue, should be fixed with 1.0.1!

[gucki]

Great, thanks a lot! 👍