On Tue, 29.05.12 22:29, Lennart Poettering (lenn...@poettering.net) wrote:
On Mon, 28.05.12 20:33, Marti Raudsepp (ma...@juffo.org) wrote:
Hi list,
Long story short, I believe there are two problems with journald:
1) journald gets stuck in an infinte loop, trying to send the message
---
TODO |2 +-
src/journal/journalctl.c | 26 +-
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/TODO b/TODO
index 3b3c451..f55a586 100644
--- a/TODO
+++ b/TODO
@@ -39,7 +39,7 @@ Features:
- graphical sessions will show a
doesn't need to include limits.h
version w/o attached
On Wed, 2012-05-30 at 09:43 -0700, Shawn Landden wrote:
---
TODO |2 +-
src/journal/journalctl.c | 26 +-
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/TODO b/TODO
With relative path handling.
I'm not sure what is meant by the other selectors, like /dev/sda
On Wed, 2012-05-30 at 09:46 -0700, shawn wrote:
doesn't need to include limits.h
version w/o attached
On Wed, 2012-05-30 at 09:43 -0700, Shawn Landden wrote:
---
TODO |
Hi,
On Wed, Apr 25, 2012 at 9:46 AM, Daniel Drake d...@laptop.org wrote:
This reverts commits d72238fcb34abc81aca97c5fb15888708ee937d3 and
f3accc08.
OLPC runs / as a bind-mount, so this must be remounted RO during
shutdown to avoid corruption.
As Lennert can't recall the exact reasons for
On Wed, May 30, 2012 at 7:17 PM, shawn shawnland...@gmail.com wrote:
With relative path handling.
Should probably do a stat() on the file in the fs and check for the
executable bit?
I'm not sure what is meant by the other selectors, like /dev/sda
Will be based on this:
On Wed, May 30, 2012 at 4:45 PM, Lennart Poettering
lenn...@poettering.net wrote:
OK, there indeed was a loop here, where we ended up processing messages
we ourselves wrote to kmsg. I have fixed that now in git. Could you test
please if this solves your problems?
Thanks. Yes, looks like this
systemd-udev is currently incorrectly labeling /run/udev/* content because it is
using selinux prefix labeling of /dev. This patch will allow systemd-udev to
use prefix labeling of /dev and /run.
From 779a7148a40f56529821d37ac348abec3b565459 Mon Sep 17 00:00:00 2001
From: Dan Walsh
Hi list,
As usual, attempting to debug one problem inevitably leads to another
bug. I found out that after filling my disk and SIGKILLing journald a
few times, it seems to corrupt the journal archive. Seems to be
reproducible every time.
journalctl reports: Failed to iterate through journal: Bad
On Wed, May 30, 2012 at 10:52 PM, Marti Raudsepp ma...@juffo.org wrote:
The two broken files (mostly consisting of zeroes) attached.
Well, they are now... :)
Regards,
Marti
broken-journal.tar.gz
Description: GNU Zip compressed data
___
systemd-devel
On Wed, 30.05.12 22:36, Marti Raudsepp (ma...@juffo.org) wrote:
Heya,
On Tue, May 29, 2012 at 11:29 PM, Lennart Poettering
lenn...@poettering.net wrote:
The journal is still very new. I think so far it is quite
stable, but there is definitely more work necessary to make it rock
solid in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-udev is currently incorrectly labeling /run/udev/* content because it is
using selinux prefix labeling of /dev. This patch will allow systemd-udev to
use prefix labeling of /dev and /run.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12
On Tue, 29.05.12 22:24, Lennart Poettering (lenn...@poettering.net) wrote:
On Sun, 27.05.12 20:15, Stephan Raue (mailingli...@openelec.tv) wrote:
Hi,
building systemd-183 with --disable-logind i get the follow error:
journald.c:(.text+0x2088): undefined reference to
On Wed, May 30, 2012 at 10:59 PM, Lennart Poettering
lenn...@poettering.net wrote:
Many people have configured their classic syslog daemon to output logs
on /dev/tty12. If you press C-s there (or accidentally hit Scroll Lock)
you end up freezing syslog too and thus freezing the entire machine
On Wed, 30.05.12 23:41, Marti Raudsepp (ma...@juffo.org) wrote:
Adding the timeout change there (which would actually be dead-easy,
simply by using SO_SNDTIMEO) would not really fix the problem too well
though: given the amount of messages that are generated the system
might not be locked
On Wed, 30.05.12 09:43, Shawn Landden (shawnland...@gmail.com) wrote:
Thanks! Applied.
I made a couple of changes afterwards: I turned around the logic so that
we check whether something is a path, and assume everything else is a
match, rather than check whether something is a match and assume
Regarding the commited version:
snip
+if (S_ISREG(st.st_mode) (0111 st.st_mode))
{
/snip
isn't it conceivable that some programs which would log would only be
executable by the owner (generally root)? because they might be suid
root? or then so we just revert to
On Wed, 30.05.12 14:06, shawn (shawnland...@gmail.com) wrote:
Regarding the commited version:
snip
+if (S_ISREG(st.st_mode) (0111 st.st_mode))
{
/snip
isn't it conceivable that some programs which would log would only be
executable by the owner (generally
On Wed, 2012-05-30 at 14:06 -0700, shawn wrote:
Regarding the commited version:
snip
+if (S_ISREG(st.st_mode) (0111 st.st_mode))
{
/snip
isn't it conceivable that some programs which would log would only be
executable by the owner (generally root)? because
On Wed, 2012-05-30 at 23:12 +0200, Lennart Poettering wrote:
On Wed, 30.05.12 14:06, shawn (shawnland...@gmail.com) wrote:
Regarding the commited version:
snip
+if (S_ISREG(st.st_mode) (0111 st.st_mode))
{
/snip
isn't it conceivable that some
On Wed, 30.05.12 16:13, Daniel J Walsh (dwa...@redhat.com) wrote:
+const char *prefixes[] = { /dev, /var/run, NULL };
Is there a reason this mentions /var/run and not /run?
Otherwise looks good to me!
Lennart
--
Lennart Poettering - Red Hat, Inc.
On Tue, May 29, 2012 at 9:39 PM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
On Tue, May 29, 2012 at 7:56 PM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
On Tue, May 29, 2012 at 12:52 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Kok, Auke-jan H at 27/05/12 08:05 did
On Wed, 30.05.12 23:32, Lennart Poettering (lenn...@poettering.net) wrote:
On Wed, 30.05.12 16:13, Daniel J Walsh (dwa...@redhat.com) wrote:
+const char *prefixes[] = { /dev, /var/run, NULL };
Is there a reason this mentions /var/run and not /run?
Otherwise looks good to me!
Heya,
http://www.freedesktop.org/software/systemd/systemd-184.tar.xz
CHANGES WITH 184:
* logind is now capable of (optionally) handling power and
sleep keys as well as the lid switch.
* journalctl now understands the syntax journalctl
/usr/bin/avahi-daemon to
It looks like dbus will need a patch upstream to work properly in the
user session, so, I'm looking at that at this time.
Is this potentially why on boot, mine might work 1 out of every 30
boots or so? I thought it was timing (and I still believe it is, I
don't know with what), but I've set up
On Thu, May 31, 2012 at 4:42 AM, Shawn Ferris shawn.fer...@gmail.com wrote:
It looks like dbus will need a patch upstream to work properly in the
user session, so, I'm looking at that at this time.
Is this potentially why on boot, mine might work 1 out of every 30
boots or so? I thought it
It would help if you could post your unit files somewhere.
tar up /usr/lib/systemd/user ?
Certainly.. here you go:
https://www.dropbox.com/s/8lxgh04jnpuecat/unit-files.tar.bz2
At this risk of not missing anything, I tar'd up all unit files..
including those included with the distro. And
27 matches
Mail list logo
