Clarify that manually setting yarp conf on WSL is not necessary if you launch yarpserver from WSL #1412
Conversation
…u launch yarpserver from WSL
Yes now it's more clear. I think that specyfing when to use these lines (i.e. to be added at the |
Feel free to suggest a better wording, see how with https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-comments-to-a-pull-request . |
|
@GiacomoBisio do you still think the working should be changed? |
| @@ -216,12 +216,14 @@ Note that you will need to restart your machine to make sure that this setting i | |||
|
|
|||
| ### Connect to a YARP server on a Windows host on WSL | |||
|
|
|||
| If you want your YARP applications on WSL to connect to a `yarpserver` that you launched on the Windows host, you need to add the following line to your WSL's `~/.bashrc`: | |||
| If you want your YARP applications on WSL to connect to a `yarpserver` that you launched on the Windows native host (so on Command Prompt, not on WSL), you need to add the following line to your WSL's `~/.bashrc`: | |||
| ~~~ | |||
| export WINDOWS_HOST=$(grep nameserver /etc/resolv.conf | awk '{print $2}') | |||
| yarp conf ${WINDOWS_HOST} 10000 > /dev/null 2>&1 | |||
| ~~~ | |||
|
|
|||
There was a problem hiding this comment.
This sentence clarifies everything
@GiacomoBisio had some strange behaviour on his PC due to this, hopefully this wording is more clear.