Matej, Vagrant doesn't disconnect the SSH session between different provisioners, so they're not picking up the change. You'll have to force Vagrant to disconnect the SSH session so it can try to reconnect. To do that, you can kill SSH and restart it or simply force kill the TCP connection using whatever OS-specific means are necessary. In that case, Vagrant will attempt to reconnect.
Best, Mitchell On Sat, Feb 15, 2014 at 1:50 AM, Matej Macak <[email protected]> wrote: > Running the following commands in the shell provisioning script does not > change the system path (as it does when this is run in the terminal). I was > using precise 64 box: > > echo 'export PATH="/usr/local/x86_64/bin:$PATH"' >> ~/.profile > > echo 'export PATH="/usr/local/x86_64/bin:$PATH"' >> ~/.bashrc > > export PATH="/usr/local/x86_64/bin:$PATH" > > > The path is neither changed during provisioning so the later commands are > not executed as if the path was modified nor are the lines from echo > commands actually inserted into the .profile or .bashrc files. Running > commands with root access (i.e. sudo) makes no difference. > > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
