If we encounter an inconsistency in a file, let's just
ignore it. Otherwise, after previous patch, we would try,
and fail, to use this file in every invocation of sd_journal_next
or sd_journal_previous that happens afterwards.
---
src/journal/sd-journal.c | 16
1 file changed, 12
On Tue, Feb 25, 2014 at 09:45:46AM +0100, Stef Walter wrote:
> While the configure correctly supports being run outside of
> the top source directory by default, it's nice if autogen.sh
> does too:
>
> $ git clone git://anongit.freedesktop.org/systemd/systemd
> $ cd systemd
> $ mkdir $(uname -m
On Wed, Feb 26, 2014 at 03:02:55PM +0100, Armin K wrote:
> They are already in nodist_systemunit_DATA and if they are
> shipped, they contain hardcoded paths to udevadm and
> systemd-udevd which will cause them to fail to start when
> rootprefix != prefix and rootlibdir != libdir.
Applied.
Zbyszek
With a corrupted file, we can get in a situation where two entries
in the entry array point to the same object. Then journal_file_next_entry
will find the first one using generic_arrray_bisect, and try to move to
the second one, but since the address is the same, generic_array_get will
return the f
On Thu, Feb 27, 2014 at 04:02:57PM +1030, Kieran Clancy wrote:
> Keymaps for Samsung 900X3E and 900X3F should be the same as for other
> models in the series.
>
> I have also moved the comment for '# Series 9' to the right place
Applied.
Zbyszek
___
sys
On Thu, Feb 20, 2014 at 03:00:09AM +0200, Uoti Urpala wrote:
> From 4775218f59474165395f7868dfbf9e6b831f5fee Mon Sep 17 00:00:00 2001
> From: Uoti Urpala
> Date: Thu, 20 Feb 2014 02:31:04 +0200
> Subject: [PATCH] logs-show: fix corrupt output with empty messages
>
> If a message had zero length,
Keymaps for Samsung 900X3E and 900X3F should be the same as for other
models in the series.
I have also moved the comment for '# Series 9' to the right place
---
hwdb/60-keyboard.hwdb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hwdb/60-keyboard.hwdb b/hwdb/60-keyboard.
On Wed, Feb 26, 2014 at 10:22 PM, Daniel J Walsh wrote:
> On 02/26/2014 03:05 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> On Wed, Feb 26, 2014 at 08:54:34PM +0100, Thomas H.P. Andersen wrote:
>>> The todo says: "something pulls in pcre as shared object dependency into
>>> our daemons such as hostnam
On Thu, 2014-02-20 at 03:00 +0200, Uoti Urpala wrote:
> If a message had zero length, journalctl would print no newline, and
Ping. There's been no reply to the above message, but it's a simple
change and I don't think the bug is one people would want to leave
unfixed.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2014 03:05 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Feb 26, 2014 at 08:54:34PM +0100, Thomas H.P. Andersen wrote:
>> The todo says: "something pulls in pcre as shared object dependency into
>> our daemons such as hostnamed"
>>
>> Norm
On Wed, Feb 26, 2014 at 08:54:34PM +0100, Thomas H.P. Andersen wrote:
> The todo says:
> "something pulls in pcre as shared object dependency into our daemons
> such as hostnamed"
>
> Normal buiild:
> ldd ./systemd-hostnamed
> linux-vdso.so.1 => (0x7fff247bc000)
> libselinux.so.1 => /
On 02/26/2014 08:54 PM, Thomas H.P. Andersen wrote:
> The todo says:
> "something pulls in pcre as shared object dependency into our daemons
> such as hostnamed"
>
> Normal buiild:
> ldd ./systemd-hostnamed
> linux-vdso.so.1 => (0x7fff247bc000)
> libselinux.so.1 => /lib64/libselinux.s
Hi Guys,
I am getting started with systemd and am looking for a particular answer. I
know the config option "StartLimitAction=" will have a pre-set option to choose
from. It either restarts the box or so. But I want to do something else as
well. For example I want to execute a script when rat
The todo says:
"something pulls in pcre as shared object dependency into our daemons
such as hostnamed"
Normal buiild:
ldd ./systemd-hostnamed
linux-vdso.so.1 => (0x7fff247bc000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x7f7ec47f7000)
librt.so.1 => /lib64/librt.so.1 (0x
Mathieu Bridon schrieb:
> On Mon, 2014-02-24 at 23:08 +0100, Lennart Poettering wrote:
>> * A new unit file option AppArmoreProfile= has been added to
>> set the AppArmor profile for the processes of a unit.
>
> I think that should be « AppArmorProfile= », not « AppArmoreProfil
They are already in nodist_systemunit_DATA and if they are
shipped, they contain hardcoded paths to udevadm and
systemd-udevd which will cause them to fail to start when
rootprefix != prefix and rootlibdir != libdir.
---
Makefile.am | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Makefile.am
'Twas brillig, and Lennart Poettering at 25/02/14 13:29 did gyre and gimble:
> On Tue, 25.02.14 13:05, Colin Guthrie ([email protected]) wrote:
>
>>
>> 'Twas brillig, and Lennart Poettering at 24/02/14 22:08 did gyre and gimble:
>>> * systemd will now understand the usual M, K, G, T suf
On Tue, 25.02.14 23:04, Khem Raj ([email protected]) wrote:
> Hi
>
> I am seeing a crash on x86
>
> systemd[1]: Set hostname to .
> systemd[1]: Initializing machine ID from random generator.
> systemd-fstab-generator[43]: Checking was requested for "rootfs", but it is
> not a device.
> systemd
18 matches
Mail list logo
