> On Nov 13, 2014, at 7:21 AM, ASF subversion and git services (JIRA)
> <j...@apache.org> wrote:
>
>
> [
> https://issues.apache.org/jira/browse/TS-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14210039#comment-14210039
> ]
>
> ASF subversion and git services commented on TS-3195:
> -----------------------------------------------------
>
> Commit ecea94131bf29d645297c41e9661a876d53fae1e in trafficserver's branch
> refs/heads/master from [~jpe...@apache.org]
> [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ecea941 ]
>
> TS-3195: initial signal handling refactor
>
> - Move features specific traffic_server from the generic signal
> handling code to traffic_server main.
> - Refactor signal handling into a small API and remove cruft for
> systems that don't support sigaction(2).
> - Move signal handling specific to traffic_server into traffic_server
> main, adopting the small signal handling API.
> - Update other apps that shared traffic_server's signal handling
> policy. In most cases, these don't need to do
> anything special with signal handling.
> - Remove (now) unused proxy.config.stack_dump_enabled.
How does that interop with existing deployments and configs? I assume we still
support both a trace like feature and allowing for a full core file generated
on the FS?
-- Leif
>
>
>> improved crash logging
>> ----------------------
>>
>> Key: TS-3195
>> URL: https://issues.apache.org/jira/browse/TS-3195
>> Project: Traffic Server
>> Issue Type: New Feature
>> Components: Core, Quality
>> Reporter: James Peach
>> Fix For: 5.2.0
>>
>>
>> Implement a crash logging helper so we can generate more sophisticated crash
>> log information. This is also an extensibility hook so that operators can
>> generate their own crash logs if they want.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
