Skip to content

Commit 5a44150

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/WSL
2 parents e7eadd9 + 77390c0 commit 5a44150

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

WSL/wsl-config.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage Linux Distributions
33
description: Reference listing and configuring multiple Linux distributions running on the Windows Subsystem for Linux.
44
keywords: BashOnWindows, bash, wsl, windows, windows subsystem for linux, windowssubsystem, ubuntu, wsl.conf, wslconfig
5-
ms.date: 05/12/2020
5+
ms.date: 03/26/2021
66
ms.topic: article
77
---
88

@@ -227,9 +227,7 @@ To reinstall, find the distribution in the Microsoft store and select "Launch".
227227

228228
> **Available in Windows Build 17093 and later**
229229
230-
Automatically configure certain functionality in WSL that will be applied every time you launch the subsystem using `wsl.conf`.
231-
232-
Right now, this includes automount options and network configuration.
230+
Automatically configure functionality in WSL that will be applied every time you launch the subsystem using `wsl.conf`. This includes automount options and network configuration.
233231

234232
`wsl.conf` is located in each Linux distribution in `/etc/wsl.conf`. If the file is not there, you can create it yourself. WSL will detect the existence of the file and will read its contents. If the file is missing or malformed (that is, improper markup formatting), WSL will continue to launch as normal.
235233

@@ -249,6 +247,8 @@ generateHosts = true
249247
generateResolvConf = true
250248
```
251249

250+
When launching multiple Linux shells for the same distribution, you must wait until the Linux subsystem stops running, this can take approximately 8 seconds after closing the last instance of the distribution shell. If you launch a distribution (ie. Ubuntu), modify the wsl.conf file, close the distribution, and then re-launch it. You might assume that your changes to the wsl.conf file have immediately gone into effect. This is not currently the case as the subsystem could still be running. You must wait ~8 seconds for the subsystem to stop before relaunching in order to give enough time for your changes to be picked up. You can check to see whether your Linux distribution (shell) is still running after closing it by using PowerShell with the command: `wsl --list --running`. If no distributions are running, you will receive the response: "There are no running distributions." You can now restart the distribution to see your wsl.conf updates applied.
251+
252252
### Configuration Options
253253

254254
In keeping with .ini conventions, keys are declared under a section.
@@ -352,4 +352,4 @@ These settings affect the VM that powers any WSL 2 distribution.
352352

353353
Entries with the `path` value must be Windows paths with escaped backslashes, e.g: `C:\\Temp\\myCustomKernel`
354354

355-
Entries with the `size` value must be a size followed by a unit, for example `8GB` or `512MB`.
355+
Entries with the `size` value must be a size followed by a unit, for example `8GB` or `512MB`.

0 commit comments

Comments
 (0)