public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/1] Disable daemon activation
Date: Tue, 5 Jun 2018 10:42:35 +0200	[thread overview]
Message-ID: <3b6ac11c-e71c-cda5-a32d-ff9ff7f207f8@ilbers.de> (raw)
In-Reply-To: <20180604112159.18605-1-claudius.heine.ext@siemens.com>

Hi Claudius,

On 06/04/2018 01:21 PM, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
> 
> Hi,
> 
> this patch disables the daemon activation in the chroot environment.
> 
> Since I could not reproduce the problem this patch handles, please test

When Alex reported this problem he mentioned that to reproduce the 
problem run './scripts/ci_build.sh -q':

<---->

-------- Forwarded Message --------
Subject: Daemons and deboostrap
Date: Sun, 27 May 2018 19:00:28 +0300
From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users <isar-users@googlegroups.com>

Hi all,

testing patches from mailing list I've found the problem with the 
current next: there are lots of daemons remain running after build is 
complete (./scripts/ci_build.sh -q).

<---->


Kind regards,
Maxim.


> if this fixes it, if the code looks fine.
> 
> Cheers,
> Claudius
> 
> Claudius Heine (1):
>    meta/isar-bootstrap: deactivate daemon activation in chroot
>      environment
> 
>   meta/classes/isar-bootstrap-helper.bbclass    |   2 +
>   .../isar-bootstrap/files/chroot-setup.sh      | 133 ++++++++++++++++++
>   .../isar-bootstrap/isar-bootstrap.bb          |  11 +-
>   3 files changed, 144 insertions(+), 2 deletions(-)
>   create mode 100644 meta/recipes-core/isar-bootstrap/files/chroot-setup.sh
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

  parent reply	other threads:[~2018-06-05  8:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 11:21 claudius.heine.ext
2018-06-04 11:21 ` [PATCH 1/1] meta/isar-bootstrap: deactivate daemon activation in chroot environment claudius.heine.ext
2018-06-05 11:05   ` Jan Kiszka
2018-06-04 17:36 ` [PATCH 0/1] Disable daemon activation Henning Schild
2018-06-04 17:48   ` Claudius Heine
2018-06-04 18:02     ` Henning Schild
2018-06-05  8:42 ` Maxim Yu. Osipov [this message]
2018-06-05 11:52   ` Claudius Heine
2018-06-05 12:38     ` Maxim Yu. Osipov
2018-06-05 12:45       ` Claudius Heine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3b6ac11c-e71c-cda5-a32d-ff9ff7f207f8@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox