Issue with Vagrant 1.1.5, VirtualBox and synced folders

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mark Kremer-2
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running
"vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to
bring up the Vagrant box, but obviously disallows me to use nfs sharing
with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.


Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mitchell Hashimoto
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Matrix Mole
I experienced the same error with 1.1.5, downloaded and installed 1.1.4 and it works fine (didn't try removing the /vagrant synced folder as wanted to confirm if it was 1.1.5 only issue, which appears to be the case). The Vagrantfile that was being used is the one located at:
https://github.com/discourse/discourse/blob/master/Vagrantfile

On Tuesday, April 2, 2013 9:29:52 PM UTC-7, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="c7wqgO_qsTIJ">ma...@...> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="c7wqgO_qsTIJ">vagrant-up+...@googlegroups.com.
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Markus Fömpe
In reply to this post by Mitchell Hashimoto
Hi,

I get the same error message on OSX with a fresh installed Vagrant 1.1.5, VirtualBox 4.2.10 and the Discourse Vagrantfile

Best regards,
Markus

Am Mittwoch, 3. April 2013 06:29:52 UTC+2 schrieb Mitchell Hashimoto:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="c7wqgO_qsTIJ">ma...@...> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="c7wqgO_qsTIJ">vagrant-up+...@googlegroups.com.
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mark Kremer
In reply to this post by Mitchell Hashimoto
Mitchell,

Of course! Here they are (there's one in my ~/.vagrant.d and one in my project): https://gist.github.com/mkremer/5304090

Like others have said the same files work fine in 1.1.4

Regards,
Mark

On 04/03/2013 06:29 AM, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mitchell Hashimoto
Mark,

I responded to your issue on GitHub but you need the "id: "vagrant-root"" option.

Best,
Mitchell


On Wed, Apr 3, 2013 at 11:51 AM, Mark Kremer <[hidden email]> wrote:
Mitchell,

Of course! Here they are (there's one in my ~/.vagrant.d and one in my project): https://gist.github.com/mkremer/5304090

Like others have said the same files work fine in 1.1.4

Regards,
Mark


On 04/03/2013 06:29 AM, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mark Kremer
Hello Mitchell,

I was a little confused about your reply since I didn't open an issue on GitHub, and then I found https://github.com/mitchellh/vagrant/issues/1538 entered by someone else mentioning my config files :)

Am I correct in understanding (based on https://github.com/mitchellh/vagrant/blob/master/config/default.rb) that /vagrant is automatically mapped even if it is not in your own Vagrantfile?

Regards,
Mark

On 05-04-2013 01:25, Mitchell Hashimoto wrote:
Mark,

I responded to your issue on GitHub but you need the "id: "vagrant-root"" option.

Best,
Mitchell


On Wed, Apr 3, 2013 at 11:51 AM, Mark Kremer <[hidden email]> wrote:
Mitchell,

Of course! Here they are (there's one in my ~/.vagrant.d and one in my project): https://gist.github.com/mkremer/5304090

Like others have said the same files work fine in 1.1.4

Regards,
Mark


On 04/03/2013 06:29 AM, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mitchell Hashimoto
Mark,

That's correct.

Best,
Mitchell


On Fri, Apr 5, 2013 at 12:23 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell,

I was a little confused about your reply since I didn't open an issue on GitHub, and then I found https://github.com/mitchellh/vagrant/issues/1538 entered by someone else mentioning my config files :)

Am I correct in understanding (based on https://github.com/mitchellh/vagrant/blob/master/config/default.rb) that /vagrant is automatically mapped even if it is not in your own Vagrantfile?

Regards,
Mark


On 05-04-2013 01:25, Mitchell Hashimoto wrote:
Mark,

I responded to your issue on GitHub but you need the "id: "vagrant-root"" option.

Best,
Mitchell


On Wed, Apr 3, 2013 at 11:51 AM, Mark Kremer <[hidden email]> wrote:
Mitchell,

Of course! Here they are (there's one in my ~/.vagrant.d and one in my project): https://gist.github.com/mkremer/5304090

Like others have said the same files work fine in 1.1.4

Regards,
Mark


On 04/03/2013 06:29 AM, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mark Kremer
Mitchell,

Alright, that makes perfect sense then! Thank you for responding! :)

Time to upgrade to 1.1.5 and update my configuration!

Regards,
Mark

On 05-04-2013 21:56, Mitchell Hashimoto wrote:
Mark,

That's correct.

Best,
Mitchell


On Fri, Apr 5, 2013 at 12:23 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell,

I was a little confused about your reply since I didn't open an issue on GitHub, and then I found https://github.com/mitchellh/vagrant/issues/1538 entered by someone else mentioning my config files :)

Am I correct in understanding (based on https://github.com/mitchellh/vagrant/blob/master/config/default.rb) that /vagrant is automatically mapped even if it is not in your own Vagrantfile?

Regards,
Mark


On 05-04-2013 01:25, Mitchell Hashimoto wrote:
Mark,

I responded to your issue on GitHub but you need the "id: "vagrant-root"" option.

Best,
Mitchell


On Wed, Apr 3, 2013 at 11:51 AM, Mark Kremer <[hidden email]> wrote:
Mitchell,

Of course! Here they are (there's one in my ~/.vagrant.d and one in my project): https://gist.github.com/mkremer/5304090

Like others have said the same files work fine in 1.1.4

Regards,
Mark


On 04/03/2013 06:29 AM, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Vagrant 1.1.5, VirtualBox and synced folders

Mark Kremer
In reply to this post by Mitchell Hashimoto
Looking at my v1 config file I now understand why it works, as that specifies the id as the first parameter. If I recall correctly that line was automatically generated (and I modified it to enable nfs). I'm not sure why my v2 config file worked in 1.1.4 though...

I think it would be a useful feature if Vagrant could automatically overwrite config based on guest path matching as you suggest in the issue, perhaps as a configurating setting. I like the way that Vagrant works now though, using the ids of the synced folders you can overwrite them as you choose (perhaps even changing their guest paths?) :)

Thanks again for taking the time to explain how this works! I really should find some time to read through the Vagrant source code... :)

      On 05-04-2013 21:56, Mitchell Hashimoto wrote:
Mark,

That's correct.

Best,
Mitchell


On Fri, Apr 5, 2013 at 12:23 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell,

I was a little confused about your reply since I didn't open an issue on GitHub, and then I found https://github.com/mitchellh/vagrant/issues/1538 entered by someone else mentioning my config files :)

Am I correct in understanding (based on https://github.com/mitchellh/vagrant/blob/master/config/default.rb) that /vagrant is automatically mapped even if it is not in your own Vagrantfile?

Regards,
Mark


On 05-04-2013 01:25, Mitchell Hashimoto wrote:
Mark,

I responded to your issue on GitHub but you need the "id: "vagrant-root"" option.

Best,
Mitchell


On Wed, Apr 3, 2013 at 11:51 AM, Mark Kremer <[hidden email]> wrote:
Mitchell,

Of course! Here they are (there's one in my ~/.vagrant.d and one in my project): https://gist.github.com/mkremer/5304090

Like others have said the same files work fine in 1.1.4

Regards,
Mark


On 04/03/2013 06:29 AM, Mitchell Hashimoto wrote:
Mark,

Can you show me the Vagrantfile that was having an error?

Best,
Mitchell


On Tue, Apr 2, 2013 at 9:29 PM, Mark Kremer <[hidden email]> wrote:
Hello Mitchell (and everyone else on the list),

I just installed the recently released 1.1.5 version, when running "vagrant up" on my v2 configurations I get the following error output:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A shared folder guest path is used multiple times. Shared
folders must all map to a unique guest path: /vagrant

Removing the /vagrant synced folder from my configuration allows me to bring up the Vagrant box, but obviously disallows me to use nfs sharing with it.

v1 configurations do no seem to have the problem.

Regards,
Mark

--
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.