[ 
https://issues.apache.org/jira/browse/TS-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach resolved TS-1892.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 3.3.3
         Assignee: James Peach

Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/f17658ac
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/f17658ac
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/f17658ac

Branch: refs/heads/master
Commit: f17658ac4d8b55a2a558ae1cc988a2295d3b1b77
Parents: 0746694
Author: James Peach <[email protected]>
Authored: Fri May 10 15:47:51 2013 -0700
Committer: James Peach <[email protected]>
Committed: Mon May 13 10:26:17 2013 -0700

{code}
----------------------------------------------------------------------
CHANGES                                  |    2 +
configure.ac                             |    1 +
iocore/eventsystem/P_UnixSocketManager.h |   25 ---------
iocore/eventsystem/SocketManager.cc      |   67 -------------------------
iocore/hostdb/MultiCache.cc              |   16 +++---
lib/ts/ink_memory.cc                     |   56 +++++++++++++++++++++
lib/ts/ink_memory.h                      |   52 +++++++++++++++----
7 files changed, 109 insertions(+), 110 deletions(-)
----------------------------------------------------------------------
{code}
                
> move msync APIs to ink_memory.h
> -------------------------------
>
>                 Key: TS-1892
>                 URL: https://issues.apache.org/jira/browse/TS-1892
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 3.3.3
>
>
> For some reason, our msync/madvise/mlock wrappers are in the SocketManager 
> class. The right place for them is really ink_memory.h.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to