Skip to content

Commit

Permalink
Merge pull request hexojs#332 from pipirt/master
Browse files Browse the repository at this point in the history
added EPERM error on WSL to Troubleshooting
  • Loading branch information
NoahDragon authored Oct 6, 2016
2 parents f331833 + 942dc6a commit 121db81
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions source/docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,9 @@ Hexo uses [Nunjucks] to render posts ([Swig] was used in older version, which sh
Hello {{ sensitive }}
{% endraw %}
```

## ENOSPC Error (Linux)

Sometimes when running the command `$ hexo server` it returns an error:
```
Error: watch ENOSPC ...
Expand All @@ -127,6 +129,19 @@ $ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo
```
This will increase the limit for the number of files you can watch.

## EMPERM Error (Windows Subsystem for Linux)

When running `$ hexo server` in a BashOnWindows environment, it returns the following error:
```
Error: watch /path/to/hexo/theme/ EMPERM
```
Unfortunately, WSL does not currently support filesystem watchers. Therefore, the live updating feature of hexo's server is currently unavailable. You can still run the server from a WSL environment by first generating the files and then running it as a static server:
``` sh
$ hexo generate
$ hexo server -s
```
This is [a known BashOnWindows issue](https://github.com/Microsoft/BashOnWindows/issues/216), and on 15 Aug 2016, the Windows team said they would work on it. You can get progress updates and encourage them to prioritize it on [the issue's UserVoice suggestion page](https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13469097-support-for-filesystem-watchers-like-inotify).

[Warehouse]: https://github.com/tommy351/warehouse
[Swig]: http://paularmstrong.github.io/swig/
[Nunjucks]: http://mozilla.github.io/nunjucks/

0 comments on commit 121db81

Please sign in to comment.