From: "Ludovic Courtès" <ludo@gnu.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: syslogd can't be started when running Guix in Docker
Date: Thu, 11 Jul 2019 23:00:09 +0200 [thread overview]
Message-ID: <87ims8p9ra.fsf@gnu.org> (raw)
In-Reply-To: <m1lfx4s9cc.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Thu, 11 Jul 2019 20:40:51 +0200")
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Do you observe similar slowness with other Docker images—e.g., Debian
>> images?
>
> No. But I don't observe any slowness with Guix either. Once it's up and
> running, performance is normal (except for the known problem with access
> to macOS file systems). It's only the daemon startup failure that
> suggests a problem. I haven't had such problems with other Docker images
> based on Debian or Ubuntu.
Hmm, it’s hard to draw any conclusion though, because systemd can do
things concurrently, so perhaps the process startup slowness is
invisible because it’s able to perform other startup work while waiting
for daemons. (It also spawns fewer daemons because some of these are
subsumed by PID 1.)
Who knows!
Ludo’.
prev parent reply other threads:[~2019-07-11 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 17:16 syslogd can't be started when running Guix in Docker Konrad Hinsen
2019-07-03 5:10 ` Maxim Cournoyer
2019-07-03 8:12 ` Konrad Hinsen
2019-07-03 11:17 ` Konrad Hinsen
2019-07-04 13:10 ` Maxim Cournoyer
2019-07-04 15:39 ` Konrad Hinsen
2019-07-05 18:22 ` Maxim Cournoyer
2019-07-05 22:25 ` Ludovic Courtès
2019-07-06 6:26 ` Konrad Hinsen
2019-07-11 15:35 ` Ludovic Courtès
2019-07-11 18:40 ` Konrad Hinsen
2019-07-11 21:00 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ims8p9ra.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).