Quoting Alan Mizrahi <alan+crux@mizrahi.com.ve>:
So we have two options: 1. Start writing init scripts properly 2. Start using start-stop-daemon
Throwing it over the fence to some poorly-conceived one-size-fits-all blackhole is not really doing anyone any favors. The biggest problem with start-stop-daemon is that it sucks and isn't reliable anyway. Hell, its unsuitability for its task is part of the motivation for these guys to switch to systemd (which addresses this problem by requiring that upstream or packagers implement logic appropriate for the daemon in question). Honestly, I have to ask why someone would go to the trouble of being a port maintainer if they're unwilling to, you know, maintain. As it stands, when looking at an init script, seeing the command "start-stop-daemon" is akin to seeing the words "magic goes here, good luck debugging anything". khm