From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: Daemons and deboostrap
Date: Wed, 30 May 2018 19:30:44 +0200 [thread overview]
Message-ID: <f4502b15-0c15-9ac1-1ecd-c049b6eeb3bc@siemens.com> (raw)
In-Reply-To: <dbdfb6c8-8a01-ed76-cc4d-421a514c0e9c@ilbers.de>
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.
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.
Jan
next prev parent reply other threads:[~2018-05-30 17:30 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 [this message]
2018-06-01 6:42 ` Claudius Heine
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=f4502b15-0c15-9ac1-1ecd-c049b6eeb3bc@siemens.com \
--to=jan.kiszka@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