[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-1567: -- Sprint: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3, Q3 Sprint 4 (was: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3) > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user id when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1567: - Sprint: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3 (was: Q3 Sprint 1, Q3 Sprint 2) > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user id when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Hindman updated MESOS-1567: Shepherd: Benjamin Mahler > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user id when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1567: - Story Points: 1 > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user id when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1567: - Sprint: Q3 Sprint 1, Q3 Sprint 2 (was: Q3 Sprint 1) > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user id when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-1567: --- Description: We currently do not log the user id when receiving a SIGTERM, this makes debugging a bit difficult. It's easy to get this information through sigaction. (was: We currently do not log the user pid when receiving a SIGTERM, this makes debugging a bit difficult. It's easy to get this information through sigaction.) > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user id when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1567: - Sprint: Q3 Sprint 1 > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user pid when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1567: - Summary: Add logging of the user uid when receiving SIGTERM. (was: Add logging of the user pid when receiving SIGTERM.) > Add logging of the user uid when receiving SIGTERM. > --- > > Key: MESOS-1567 > URL: https://issues.apache.org/jira/browse/MESOS-1567 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Benjamin Mahler >Assignee: Alexandra Sava > > We currently do not log the user pid when receiving a SIGTERM, this makes > debugging a bit difficult. It's easy to get this information through > sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
