Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel Roach <nroach44@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/systemd: journald should use volatile storage
Date: Sun,  1 Mar 2015 17:10:58 +0800	[thread overview]
Message-ID: <1425201058-3946-1-git-send-email-nroach44@gmail.com> (raw)

(By default)

This fixes https://bugs.busybox.net/show_bug.cgi?id=7892

Journald was attempting to write the logs to file before the
underlying file system was up. A proposed solution was to bring
/tmp up beforehand, but that did not always solve the issue.

In addition, since the logging directory was a tmpfs to begin with
(/var/log -> /tmp) this should save some cycles.

Signed-off-by: Nathaniel Roach <nroach44@gmail.com>
---
 package/systemd/0004-fix-journald-on-tmpfs.patch | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 package/systemd/0004-fix-journald-on-tmpfs.patch

diff --git a/package/systemd/0004-fix-journald-on-tmpfs.patch b/package/systemd/0004-fix-journald-on-tmpfs.patch
new file mode 100644
index 0000000..c143e47
--- /dev/null
+++ b/package/systemd/0004-fix-journald-on-tmpfs.patch
@@ -0,0 +1,12 @@
+--- systemd-218.orig/src/journal/journald.conf
++++ systemd-218/src/journal/journald.conf
+@@ -11,7 +11,7 @@
+ # See journald.conf(5) for details
+ 
+ [Journal]
+-#Storage=auto
++Storage=volatile
+ #Compress=yes
+ #Seal=yes
+ #SplitMode=uid
+
-- 
2.1.4

             reply	other threads:[~2015-03-01  9:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01  9:10 Nathaniel Roach [this message]
2015-03-01 20:44 ` [Buildroot] [PATCH 1/1] package/systemd: journald should use volatile storage Peter Korsgaard
2015-03-02 17:13   ` Mike Williams
2015-07-26 22:19     ` Maxime Hadjinlian
2015-07-27  2:27       ` Nathaniel Roach
2015-07-27  7:54         ` Maxime Hadjinlian

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=1425201058-3946-1-git-send-email-nroach44@gmail.com \
    --to=nroach44@gmail.com \
    --cc=buildroot@busybox.net \
    /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