Stowage/caddy
2
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-10-20 00:03:17 +00:00
Code Issues Projects Releases Packages Wiki Activity

cmd: Eliminate unintended use of cgo

Browse source 
This means the stop command can only use the API to stop the instance;
no more signaling, unless we find a cgo-free way of doing it.
This commit is contained in:
Matthew Holt 2019-12-23 12:41:05 -07:00
parent 724c728678
commit cbb405f6aa
No known key found for this signature in database
GPG key ID: 2A349DD577D586A5
4 changed files with 5 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

10
cmd/commands.go
View file

@ -134,13 +134,9 @@ not quit after printing, and can be useful for troubleshooting.`,
Long: `
Stops the background Caddy process as gracefully as possible.
It will first try to use the admin API's /stop endpoint; the address of
this request can be customized using the --address flag if it is not the
default.
If that fails for any reason, it will attempt to signal the first process
it can find named the same as this one (os.Args[0]). On Windows, such
a stop is forceful because Windows does not have signals.`,
It requires that the admin API is enabled and accessible, since it will
use the API's /stop endpoint. The address of this request can be
customized using the --address flag if it is not the default.`,
Flags: func() *flag.FlagSet {
fs := flag.NewFlagSet("stop", flag.ExitOnError)
fs.String("address", "", "The address to use to reach the admin API endpoint, if not the default")