Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 76A7A200CE0 for ; Thu, 27 Jul 2017 04:38:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7373316A083; Thu, 27 Jul 2017 02:38:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BA30316A080 for ; Thu, 27 Jul 2017 04:38:07 +0200 (CEST) Received: (qmail 48864 invoked by uid 500); 27 Jul 2017 02:38:06 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 48849 invoked by uid 99); 27 Jul 2017 02:38:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2017 02:38:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E33311A09A7 for ; Thu, 27 Jul 2017 02:38:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id PbJsNp0TXPNN for ; Thu, 27 Jul 2017 02:38:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A51F85FD3D for ; Thu, 27 Jul 2017 02:38:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7F0B4E00A3 for ; Thu, 27 Jul 2017 02:38:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 12DCB24D23 for ; Thu, 27 Jul 2017 02:38:00 +0000 (UTC) Date: Thu, 27 Jul 2017 02:38:00 +0000 (UTC) From: "y123456yz (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MESOS-7813) when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 27 Jul 2017 02:38:08 -0000 [ https://issues.apache.org/jira/browse/MESOS-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101065#comment-16101065 ] y123456yz edited comment on MESOS-7813 at 7/27/17 2:37 AM: ----------------------------------------------------------- [~jvanremoortere] thanks very much. 1. my lxc-start is started by my Executor, lxc-start running with"/usr/bin/lxc-start -f /xxx/config -n xxx", Executor running with "/usr/bin/Executor xxxx", they started by command lines, not through systemd service. whther I should start my Executor and lxc by systemd service(add delegate=true)? now, I start them by command lines, not by systemd service, as following: /usr/bin/my-Executor -f xxx -d & /usr/bin/lxc-start -f config -n xxx & if must add "delegate=true", how to add "delegate=true" when I start my Executor and lxc-start by command lines. 2. there have another problem, sometimes, when I restart mesos service, the lxc container stoped automaticly. thanks again, Joris Van Remoortere was (Author: y123456yz): [~jvanremoortere] thanks very much. there have another problem, sometimes, when I restart mesos service, the lxc container(lxc-start is started by my Executor, lxc-start running with"/usr/bin/lxc-start -f /xxx/config -n xxx", Executor running with "/usr/bin/Executor xxxx", they started not through systemd service) stoped automaticly. whther I should start my Executor and lxc by systemd service(add delegate=true)? now, I start them by command lines, not by systemd service, as following: /usr/bin/my-Executor -f xxx -d & /usr/bin/lxc-start -f config -n xxx & thanks again, Joris Van Remoortere > when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why? > -------------------------------------------------------------------------------------------------------------------------- > > Key: MESOS-7813 > URL: https://issues.apache.org/jira/browse/MESOS-7813 > Project: Mesos > Issue Type: Bug > Components: agent, cgroups, executor, framework > Environment: 1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > Reporter: y123456yz > > when lxc run after a period of time, the file(/proc/pid/cgroup) is modified, devices,blkio,memory,cpuacct is changed. why? -- This message was sent by Atlassian JIRA (v6.4.14#64029)