0534fbada8
Users following the installation guide sometimes get stuck, reporting that Elasticsearch has "hung" after running `./bin/elasticsearch` because it doesn't exit, it just sits there in the foreground waiting for something to happen. We do say that it "runs in the foreground" in the docs but that's not clear enough, maybe folks expect it to declare it started up successfully or to open a browser window for them or something. This commit expands the docs to clarify what users should expect from running Elasticsearch from the command line and what they should do next. |
||
|---|---|---|
| .. | ||
| brew.asciidoc | ||
| check-running.asciidoc | ||
| deb.asciidoc | ||
| docker-compose.yml | ||
| docker.asciidoc | ||
| etc-elasticsearch.asciidoc | ||
| key.asciidoc | ||
| license.asciidoc | ||
| msi-windows-start.asciidoc | ||
| next-steps.asciidoc | ||
| rpm.asciidoc | ||
| skip-set-kernel-parameters.asciidoc | ||
| sysconfig-file.asciidoc | ||
| systemd.asciidoc | ||
| targz-daemon.asciidoc | ||
| targz-start.asciidoc | ||
| targz.asciidoc | ||
| windows.asciidoc | ||
| xpack-indices.asciidoc | ||
| zip-windows-start.asciidoc | ||
| zip-windows.asciidoc | ||