You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Hindman (JIRA)" <ji...@apache.org> on 2012/05/29 22:52:23 UTC

[jira] [Created] (MESOS-200) New Linux 'proc' code assuming too new a kernel.

Benjamin Hindman created MESOS-200:
--------------------------------------

             Summary: New Linux 'proc' code assuming too new a kernel.
                 Key: MESOS-200
                 URL: https://issues.apache.org/jira/browse/MESOS-200
             Project: Mesos
          Issue Type: Bug
            Reporter: Benjamin Hindman
            Assignee: Benjamin Hindman
            Priority: Blocker


We should assume an older kernel and remove some of the new bits that were added for more recent kenels (or make them be optional).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (MESOS-200) New Linux 'proc' code assuming too new a kernel.

Posted by "Benjamin Hindman (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MESOS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Hindman resolved MESOS-200.
------------------------------------

    Resolution: Fixed
    
> New Linux 'proc' code assuming too new a kernel.
> ------------------------------------------------
>
>                 Key: MESOS-200
>                 URL: https://issues.apache.org/jira/browse/MESOS-200
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Benjamin Hindman
>            Assignee: Benjamin Hindman
>            Priority: Blocker
>
> We should assume an older kernel and remove some of the new bits that were added for more recent kenels (or make them be optional).

--
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