[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-23016: ------------------------------------------- To add my 0.02$. As already mentioned, we have to differentiate between OS X / Linux and Windows. On the former Landrush uses sudo to make some changes to system files ({{/etc/resolver}} for OS X and {{/etc/dnsmasq.d}} resp. {{/etc/resolv.conf}}). This changes are required in order to (re-)-configure the host DNS in order to resolve the OpenShift IP. If the {{vagrant up}} process is not interactive this is an issue. Can it be made interactive? As a workaround, the user would indeed need to start the system once from the command line to create/modify the necessary files. After that {{vagrant up}} will also work from Eclipse. On Windows, the case it different. One also needs admin privileges, but there is no concept of sudo. There some Windows tools are executed which require admin privileges to be run. In order to do that, the Ruby script which calls these tools will try to elevate to admin mode. If the user has admin privileges this will be transparent (you might see a window pop up and disappear, but no interaction required). If the user does not have the privileges, the default Windows dialog to provide admin credentials pops up. It is unfortunate that this happens multiple times, but as mentioned it is not only Landrush which required admin privileges, but also VirtualBox. Personally, I would expect to have admin privileges on the development machine, but I guess in some corporate settings this might be wishful thinking. However, in this case they might not even mind that they have to provide credentials multiple times. {quote} BTW, does anybody know how to get back to the state where landrush needs to make these changes which require admin permissions? I mean how to recreate the first time use of landrush. {quote} * OS X - Remove the file created in {{/etc/resolver/}} * Linux - Remove generated file in {{/etc/dnsmasq.d}} and revert {{/etc/resolv.conf}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)