From: Claudius Heine <ch@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: Daemons and deboostrap
Date: Fri, 01 Jun 2018 08:42:59 +0200 [thread overview]
Message-ID: <d63d7b82d38bda83679fd623a175ebdcc0a7c425.camel@denx.de> (raw)
In-Reply-To: <f4502b15-0c15-9ac1-1ecd-c049b6eeb3bc@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]
Hi,
On Wed, 2018-05-30 at 19:30 +0200, Jan Kiszka wrote:
> On 2018-05-27 21:30, Alexander Smirnov wrote:
> > On 05/27/2018 07:00 PM, Alexander Smirnov wrote:
> > > 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).
> > >
> > > 8<--
> > >
> > > $ ps ax
> > > ...
> > > 24785 ? Ssl 0:00 /usr/bin/qemu-arm-static
> > > /usr/sbin/sshd
> > > 25085 ? Ssl 0:00 /usr/bin/qemu-arm-static
> > > /usr/bin/dbus-daemon --system
> > > 3046 ? Ssl 0:00 /usr/bin/qemu-arm-static
> > > /usr/bin/dbus-daemon --system
> > > 4582 ? Ss 0:00 /usr/bin/dbus-daemon --system
> > > 8577 ? Ssl 0:00 /usr/bin/qemu-arm-static
> > > /usr/bin/dbus-daemon --system
> > > ...
> > >
> > > 8<--
> > >
> >
> > CI server contains tens of dbus processes, so it's not the issue of
> > my
> > host.
>
> Likely not noticed by us here as we usually build in containers, and
> they tear down those daemons once your build is done.
I normally don't exit the container after a build so it should be
happening there as well, but it didn't for me.
I might have to spend some time testing with different packages in
order to reproduce this, but I am pretty sure I tried installing
openssh before.
> That said, seems reasonable to restore some daemon startup prevention
> then, maybe now with clearer comments why that is needed - I vaguely
> recall an internal discussion where the reasons for the existence of
> that measures remain open.
Since installing debian via chroot and debootstrap is one of the
official supported ways of doing it, I would suspect that starting
daemons within that environment should be prevented upstream.
Maybe take a look at how the debian-installer handles this?
Cheers,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-01 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 16:00 Alexander Smirnov
2018-05-27 19:30 ` Alexander Smirnov
2018-05-30 17:30 ` Jan Kiszka
2018-06-01 6:42 ` Claudius Heine [this message]
2018-06-01 7:22 ` 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=d63d7b82d38bda83679fd623a175ebdcc0a7c425.camel@denx.de \
--to=ch@denx.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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