This is supposed to be a blocker bug for
to come up with a nicer/global way of handling figuring out why a port doesn't startup.
Right now, if a port/service doesn't start for whatever reason, other than sh -x <rc script> one is sort of left out in the cold. A lot of services that use daemon have the -f flag, which outputs to /dev/null which further complicates tracking down why some service didn't startup.
* Possible Solution
Have a service name debug command, that when run would set -x and redirect stderr/stdout from the service in question to the controlling tty.
This particular solution would likely require touching /usr/sbin/daemon and service.
Other/better thoughts and solutions are encouraged.
No patches or proof of concept(s) are created at this time.
Add DEBUG_SCRIPT=yes to pkg.conf and you have exactly that.
I do mean