All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Holger Hans Peter Freyther <holger@moiji-mobile.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: State of systemd from an integrator point of view
Date: Mon, 18 Feb 2013 13:14:47 +0000	[thread overview]
Message-ID: <CAJTo0LZ5iGazfVfmu225HShMJ7AeLWSixtkkGmEwKU0XYMQhKA@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LbOcDd5N6Be=sYrEEJdPoPtX5Cw+tnze=0DAhjp53M7hg@mail.gmail.com>

On 18 February 2013 13:10, Burton, Ross <ross.burton@intel.com> wrote:
>> * systemd's journald is not suitable for small devices. I think the default
>> should be to disable the journald and do not disable the busybox log
>> application in the systemd-compat units package. journald is dominated by
>> memory allocations and reading procfs over and over again.
>
> Agreed, although it would be good if the journal could be tuned.  IMHO
> it's technically great, just young.
>
> I wonder if we can split out the bulk of the journal binaries into a
> separate package, so by default it's disabled and then installing
> systemd-journal would enable it.

Just noticed that the disabling of syslog isn't working for me, it
disables syslog-busybox but there's a syslog symlink to it, which is
being started. :)

Ross



  reply	other threads:[~2013-02-18 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 10:24 State of systemd from an integrator point of view Holger Hans Peter Freyther
2013-02-18 13:10 ` Burton, Ross
2013-02-18 13:14   ` Burton, Ross [this message]
2013-02-18 15:08     ` Holger Hans Peter Freyther
2013-02-18 15:27   ` Holger Hans Peter Freyther

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=CAJTo0LZ5iGazfVfmu225HShMJ7AeLWSixtkkGmEwKU0XYMQhKA@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=holger@moiji-mobile.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.