Comment 9 for bug 809646

Soren, I do think init.d 'stop' should do what swift-init 'stop' does, which is the 'stop now, closing any connections' action. The 'shutdown' is optional for the init.d scripts, but it is used pretty often during upgrades and such.

Thomas, you're right that 'shutdown' isn't a standard parameter of the init.d. I'm not sure on the policy for adding another option. As far as the difference, 'stop' will exit immediately closing any connections, 'shutdown' will stop listening immediately and exit once existing connections have been satisfied (long running uploads/downloads etc. can take quite some time).

For swift-init, 'restart' will do the equivalent of a 'stop' and 'start' with as little time in between as possible.

For swift-init, 'reload' will do the equivalent of a 'shutdown' and 'start' with as little time in between as possible.

If you want to get rid of swift-init completely for your packaging here, you're certainly welcome to. You can call swift-proxy-server directory for instance. SIGHUP is the graceful shutdown, SIGTERM is the stop, that sort of thing. I wouldn't recommend that path, but I'm also not the packager: those who do the work, get the final say. :)