Cutlery/caddy
1
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-06-23 15:31:40 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Typo: change foreful to forceful

William Asper 2019-12-30 19:24:21 -08:00
parent 635a02efeb
commit cc3c37cdb5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
v2:-Documentation.md

@ -156,7 +156,7 @@ $ caddy stop [--address <interface>]
Gracefully stops the running Caddy process (other than the process for the stop command) and causes it to exit.
It first tries to use the admin API (at its default address, or you can customize it with the `--address` flag) to perform a graceful shutdown. In other words, it simply performs a request to the [/stop endpoint](#post-stop). If that fails for any reason, it will look for any other process named the same as the current binary (i.e. `os.Args[0]`) and signal it to stop gracefully. On Windows, such a stop is foreful and Caddy will not have an opportunity to clean up any active locks.
It first tries to use the admin API (at its default address, or you can customize it with the `--address` flag) to perform a graceful shutdown. In other words, it simply performs a request to the [/stop endpoint](#post-stop). If that fails for any reason, it will look for any other process named the same as the current binary (i.e. `os.Args[0]`) and signal it to stop gracefully. On Windows, such a stop is forceful and Caddy will not have an opportunity to clean up any active locks.
If you want to stop the current configuration but do not want to exit the process, use the admin API: [`DELETE /config/`](#delete-configscope).