[Bug 239144] Identify generic RC framework extensions to improve ports script debugging

[bugzilla-noreply at freebsd.org]

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

--- Comment #6 from Tara <tara at anne.cat> ---
Baptiste: all it does is add the -x for you, but does nothing for getting the
output from the service executable yourself, and it's a GLOBAL flag, so once
you set it, you get output from *every* service from then on.  I'm proposing a
per-service debug, that works for figuring out why 1 particular service is
being mean and not starting.

(In reply to Pietro Cerutti from comment #5)
1) I'm new to FreeBSD changes, I'm happy to do whatever is best.

2) I only did 3 ports, to sort of show off the idea, without expending lots of
resources. If it's well accepted I'm happy to expend some more resources.

3) if we do it piecemeal, we get more chances at support across the ports tree
and a better chance of finding where my idea will screw up long before it
becomes default across the entire ports tree.  i.e. More ports people will see
the commits against their particular port they maintain(or so I would think..
please tell me if I'm wrong).

Every port that uses daemon, doesn't necessarily do it the same way (these 3 I
picked don't all run daemon the same way for instance).  A giant commit across
the entire daemon using ports tree would be a lot of work all at once (since
automating it would be difficult).  So piecemeal I can just push commits as I
find a spare few minutes.

Also for services that don't use daemon(of which there are many), every single
port will require some special unique fix I'm sure.  I haven't started looking
at those yet.

I'd love to be proven wrong :)

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