[Bug 239144] make debugging of ports very easy, or at least easier.

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239144

            Bug ID: 239144
           Summary: make debugging of ports very easy, or at least easier.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: tara at anne.cat

This is supposed to be a blocker bug for

#239126
#239127
#239124

to come up with a nicer/global way of handling figuring out why a port doesn't
startup.

* Problem:

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.

* Status

No patches or proof of concept(s) are created at this time.

-- 
You are receiving this mail because:
You are the assignee for the bug.