This patch adds support for RFC 5424 syslog format to journald. Journald
can now forward logs to a multicast UDP group.
RFC 5424 format:
VERSION SP TIMESTAMP SP HOSTNAME SP APP-NAME SP PROCID SP MSGID SP
[SD-ID]s SP MSG
Example conf:
file: journald.conf
SysLogAddress=239.0.0.1:6000
---
Makefile
On Tue, Feb 17, 2015 at 12:06 AM, Oliver Neukum wrote:
>
> On Mon, 2015-02-16 at 14:52 -0800, Hans Scholze wrote:
> > Hi,
> >
> >
> > I'm not sure if this is considered a problem but I noticed some
> > spurious error messages during boot. The source appears to be:
> >
> >
> > 1. a USB media card
Hey Lubomir,
Lubomir Rintel [2015-02-18 21:02 +0100]:
> Some (all? -- an equivalent rule exists for X200t already) ThinkPad tablet
> firmware has DMI product name and version reversed:
>
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: LENOVO
> Product Na
Hey Sergey,
Sergey Ptashnick [2015-02-19 3:32 +0300]:
> Add strings for fsckd.
Applied, thanks!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
___
systemd-de
В Wed, 18 Feb 2015 21:48:48 +0100
Tom Gundersen пишет:
> On Wed, Feb 18, 2015 at 9:36 PM, Reindl Harald wrote:
> > Am 18.02.2015 um 21:29 schrieb Giancarlo Razzolini:
> >> It is my perception that if you are using predictable network interface
> >> naming, which is the current default, you can s
---
fs.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs.c b/fs.c
index 22ca62b..f751392 100644
--- a/fs.c
+++ b/fs.c
@@ -208,7 +208,6 @@ static struct inode *fs_inode_get(struct super_block *sb,
inode->i_private = kdbus_node_ref(node);
inode->i_mapping->a_ops = &empty_aops
Add strings for fsckd.
---
po/ru.po |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/po/ru.po b/po/ru.po
index f07f333..1ffeec6 100644
--- a/po/ru.po
+++ b/po/ru.po
@@ -7,7 +7,7 @@ msgstr ""
"Project-Id-Version: systemd\n"
"Report-Msgid-Bugs-To: 0comff...@inbox.ru\
2015-02-19 0:39 GMT+01:00 Zbigniew Jędrzejewski-Szmek :
> On Wed, Feb 18, 2015 at 11:52:50PM +0100, Michael Biebl wrote:
>> 2015-02-18 20:34 GMT+01:00 Lennart Poettering :
>> > Well, why patch anything? You already have a configure option, just by
>> > adding LDFLAGS= and CFLAGS= to the end of the
On Wed, Feb 18, 2015 at 11:52:50PM +0100, Michael Biebl wrote:
> 2015-02-18 20:34 GMT+01:00 Lennart Poettering :
> > Well, why patch anything? You already have a configure option, just by
> > adding LDFLAGS= and CFLAGS= to the end of the configure line. What's
> > the point of having an explicit op
2015-02-18 20:34 GMT+01:00 Lennart Poettering :
> Well, why patch anything? You already have a configure option, just by
> adding LDFLAGS= and CFLAGS= to the end of the configure line. What's
> the point of having an explicit option for that?
What is the reason to override the default linker anywa
On 18-02-2015 19:23, Lennart Poettering wrote:
> Well, if you have networking up so early that's usually because you
> need it to boot, for example because it is the backing device for the
> root file system. In such a case it would be a really bad idea to take
> the network interface down.
This i
On Wed, 18.02.15 18:26, Giancarlo Razzolini (grazzol...@gmail.com) wrote:
> On 18-02-2015 18:12, Mantas Mikulėnas wrote:
> > It's so much not that udev won't do this – the kernel actually won't
> > let it to:
> >
> > # ip link set eth0 up
> > # ip link set eth0 name fred0
> > RTNETLINK answers: De
El 18/02/15 a las 07:10, Lennart Poettering escribió:
On Tue, 17.02.15 17:35, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
Please fix this for all arguments, not just symlinks.
diff --git a/src/tmpfiles/tmpfiles.c b/src/tmpfiles/tmpfiles.c
index c948d4d..1b35b8e 100644
--- a/src/tmpfil
On 18-02-2015 19:11, Reindl Harald wrote:
> and since you say *this* is an exception you can be sure that you
> could find enough people point to this and that which explains why it
> is a bad idea - implement something which changes existing behavior
> and needs exceptions right from the start is
Am 18.02.2015 um 21:58 schrieb Giancarlo Razzolini:
On 18-02-2015 18:49, Reindl Harald wrote:
that won't change the fact that if *anybody* comes to the idea to take
an interface which *is up* down for rename it should get removed any
commit permissions instantaneously because he don't care abo
On Wed, Feb 18, 2015 at 9:58 PM, Giancarlo Razzolini
wrote:
> You are talking about userspace
> *after* initramfs and *after* systemd is initialized and renamed (or not)
> any interface. Of course systemd should *never* mess with an interface
> *after* system initialization. But it can do anything
On 18-02-2015 18:49, Reindl Harald wrote:
> that won't change the fact that if *anybody* comes to the idea to take
> an interface which *is up* down for rename it should get removed any
> commit permissions instantaneously because he don't care about *a ton*
> of implications depending on the local
Am 18.02.2015 um 21:40 schrieb Giancarlo Razzolini:
On 18-02-2015 18:36, Reindl Harald wrote:
predictable? go away!
This does not reflect the default behavior systemd-udevd and I believe
it is your *personal* opinion.
on any machine i know running network.service (the old style)
ethX is p
On Wed, Feb 18, 2015 at 9:36 PM, Reindl Harald wrote:
> Am 18.02.2015 um 21:29 schrieb Giancarlo Razzolini:
>> It is my perception that if you are using predictable network interface
>> naming, which is the current default, you can safely make your network
>> configuration use the changed interfac
On Wed, Feb 18, 2015 at 9:10 PM, Giancarlo Razzolini
wrote:
> I am currently the maintainer and developer for some archlinux
> initramfs tools that deals with early userspace network. More precisely,
> I do develop/maintain these hooks:
>
> https://aur.archlinux.org/packages/dropbear_initr
On 18-02-2015 18:36, Reindl Harald wrote:
> predictable? go away!
This does not reflect the default behavior systemd-udevd and I believe
it is your *personal* opinion.
>
> on any machine i know running network.service (the old style)
> ethX is predictable and the new "predictable" changed multipl
Am 18.02.2015 um 21:29 schrieb Giancarlo Razzolini:
On 18-02-2015 18:19, Reindl Harald wrote:
and hopefully that keeps this way
* configurations rely on eth0, eth1... exists
Didn't you mean en, wl, etc?
no, i mean what i say
* they are sane and fine
* firewall rules may depend on them
On 18-02-2015 18:19, Reindl Harald wrote:
> and hopefully that keeps this way
>
> * configurations rely on eth0, eth1... exists
Didn't you mean en, wl, etc?
> * they are sane and fine
> * firewall rules may depend on them
It is my perception that if you are using predictable network interface
nam
On 18-02-2015 18:12, Mantas Mikulėnas wrote:
> It's so much not that udev won't do this – the kernel actually won't
> let it to:
>
> # ip link set eth0 up
> # ip link set eth0 name fred0
> RTNETLINK answers: Device or resource busy
> #
>
Thank you for your fast response, Mantas. I'm aware that this
On 14.02.2015 00:53, Zbigniew Jędrzejewski-Szmek wrote:
> We would require a match against all three: patterns specified
> with --to, with --from, and as positional arguments to show an
> edge. This does not seem useful. Let instead the positional args
> behave like they were specified in both --to
Am 18.02.2015 um 21:12 schrieb Mantas Mikulėnas:
On Wed, Feb 18, 2015 at 10:10 PM, Giancarlo Razzolini
mailto:grazzol...@gmail.com>> wrote:
But, in both cases, I need to flush the interface and set it
status to DOWN before the initramfs handle the init to systemd. I took a
look at t
On Wed, Feb 18, 2015 at 10:10 PM, Giancarlo Razzolini
wrote:
> But, in both cases, I need to flush the interface and set it
> status to DOWN before the initramfs handle the init to systemd. I took a
> look at the: src/udev/udev-builtin-net_id.c file and it seems indeed
> that it won't rename an i
Hi all,
I am currently the maintainer and developer for some archlinux
initramfs tools that deals with early userspace network. More precisely,
I do develop/maintain these hooks:
https://aur.archlinux.org/packages/dropbear_initrd_encrypt/
https://aur.archlinux.org/packages/mkinitcpio-
Some (all? -- an equivalent rule exists for X200t already) ThinkPad tablet
firmware has DMI product name and version reversed:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 7762AS1
Version: ThinkPad X61 Tablet
Serial Numbe
On Wed, 18.02.15 16:25, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
> El 18/02/15 a las 15:58, Lennart Poettering escribió:
> >On Wed, 18.02.15 15:45, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
> >
> >>LTO may be unreliable, does not work properly in several archs
> >>It may cra
El 18/02/15 a las 15:58, Lennart Poettering escribió:
On Wed, 18.02.15 15:45, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
LTO may be unreliable, does not work properly in several archs
It may crash or produce wrong code.
Well, that's something to fix in the LTO code.
Compiler devel
On Wed, 18.02.15 15:45, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
> LTO may be unreliable, does not work properly in several archs
> It may crash or produce wrong code.
Well, that's something to fix in the LTO code.
> Compiler developers also said we should not provide production
> RP
LTO may be unreliable, does not work properly in several archs
It may crash or produce wrong code.
Compiler developers also said we should not provide production
RPM packages with LTO enabled.
GOLD also does not work everywhere.
---
configure.ac | 15 ++-
1 file changed, 10 insertion
> On 18 Feb 2015, at 18:47, Lennart Poettering wrote:
>
> On Wed, 18.02.15 10:41, Thierry Parmentelat (thierry.parmente...@inria.fr)
> wrote:
>
>> root@bigjohn /vservers # journalctl -b -f
>> -- Logs begin at Fri 2014-09-05 04:28:57 CEST. --
>> Feb 18 10:38:25 bigjohn.pl.sophia.inria.fr system
On Tue, 17.02.15 16:48, Peter Paule (systemd-de...@fedux.org) wrote:
>
> Hi there,
>
> I tried "machinectl" from systemd 219 on Arch Linux (testing) today: I got
> two errors. Should we discuss this here or should I open a Bug Report?
>
> 1) Download if tar-file
> (http://www.freedesktop.org/so
On Wed, 18.02.15 10:41, Thierry Parmentelat (thierry.parmente...@inria.fr)
wrote:
> root@bigjohn /vservers # journalctl -b -f
> -- Logs begin at Fri 2014-09-05 04:28:57 CEST. --
> Feb 18 10:38:25 bigjohn.pl.sophia.inria.fr systemd[1]: Looping too fast.
> Throttling execution a little.
> Feb 18 1
Hi Lennart
On 2015-02-18 11:19, Lennart Poettering wrote:
> On Wed, 18.02.15 12:13, Joonas Sarajärvi (m...@iki.fi) wrote:
>
>
> FS_NOCOW does no effect btrfs raid settings. If you want this kind of
> data redundancy then it will continue to be available even though we
> set FS_NOCOW now.
Whitou
From: Lucas De Marchi
By notifying the clients when this property is changed it's possible to
allow "system health monitor" tools to get transitions like
running<->degraded. This is an alternative to send changes on the
SystemState property since the latter is more difficult to derive.
---
src/c
Le 18/02/2015 17:00, Martin Pitt a écrit :
Ça va Didier,
these now apply/build/check fine against master, I tested the binaries
on my laptop and in a VM, all review comments were addressed. As
discussed with Zbigniew on IRC I landed them now.
Thanks a lot Martin for doing this further testing
Ça va Didier,
these now apply/build/check fine against master, I tested the binaries
on my laptop and in a VM, all review comments were addressed. As
discussed with Zbigniew on IRC I landed them now.
A big omission is of course the lack of German translations! :-)
(I'll commit them now)
Merci,
El 18/02/15 a las 07:10, Lennart Poettering escribió:
On Tue, 17.02.15 17:35, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
Please fix this for all arguments, not just symlinks.
Thanks for taking a look, I will post a complete version later. ;)
__
On Wed, Feb 18, 2015 at 3:19 PM, Martin Pitt wrote:
> Martin Pitt [2015-02-18 15:06 +0100]:
>> I couldn't quickly find a reference for EFI variables (which is the
>> main thing we are using this for), and I don't have/know a big-endian
>> EFI machine to check this on.
>
> I had a look into the off
Martin Pitt [2015-02-18 15:06 +0100]:
> I couldn't quickly find a reference for EFI variables (which is the
> main thing we are using this for), and I don't have/know a big-endian
> EFI machine to check this on.
I had a look into the official spec
http://www.uefi.org/sites/default/files/resources/
Dnia wtorek, 17 lutego 2015 17:23:55 Lennart Poettering pisze:
> On Tue, 17.02.15 17:13, Maciej Wereski (m.were...@partner.samsung.com)
wrote:
> > Hello,
> >
> > Dnia poniedziałek, 16 lutego 2015 23:59:56 Lennart Poettering pisze:
> > > Note that this version is not available in Fedora F22/F23 ye
On Wed, Feb 18, 2015 at 11:03:39AM +0100, Lennart Poettering wrote:
> Well it's the only logic that can work really, already since the same
> device node is usually known to the kernel by a different name thatn
> to userspace. Trying to always map that is really nasty, as one can
> see with the GPT
On Wed, Feb 18, 2015 at 3:06 PM, Martin Pitt wrote:
> Hey Tom,
>
> Tom Gundersen [2015-02-18 14:34 +0100]:
>> I think we want to assume that we only get UTF-16LE, so it looks like
>> it is the test that is buggy. That's what we agreed, right Lennart?
>
> Ah, ok. Indeed GUID partition names are UTF
Hey Tom,
Tom Gundersen [2015-02-18 14:34 +0100]:
> I think we want to assume that we only get UTF-16LE, so it looks like
> it is the test that is buggy. That's what we agreed, right Lennart?
Ah, ok. Indeed GUID partition names are UTF16LE.
I couldn't quickly find a reference for EFI variables (w
On Wed, Feb 18, 2015 at 6:54 AM, Martin Pitt wrote:
> 219 shows a test failure in test-utf8 on big-endian machines (on
> Debian: powerpc, s390, mips):
>
> Assertion 'streq(a, utf8)' failed at src/test/test-utf8.c:103, function
> test_utf16_to_utf8(). Aborting.
>
> gdb shows that indeed the conver
What is the best way to set cgroup limits for user processes? I mean the
individual processes. I know that you can set limits for user.slice, but
how to set limits for, let's say, firefox?
I tried to make a service file for firefox, it looks like this:
[Unit]
Description=Firefox Web Browser
Docum
>From 59d7202a3755dd73ebad94a20921975330a4ee83 Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Mon, 26 Jan 2015 17:46:36 +0100
Subject: [PATCH 9/9] Add mock fsck process
---
test/mocks/fsck | 27 +++
1 file changed, 27 insertions(+)
create mode 100755 test/mocks/fsck
>From 9db0d5cd0cc20b899ddf77ccdfcbe214978eb463 Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Mon, 26 Jan 2015 17:34:59 +0100
Subject: [PATCH 8/9] Add man page and references to it.
Add man page explaining the plymouth theme protocol, usage of the daemon
as well as the socket activation part
>From 03f05550e81941d2073d151aaedfe3d06c1f95b0 Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Mon, 26 Jan 2015 17:23:08 +0100
Subject: [PATCH 6/9] Refresh po files
Also, add new plymouth fsckd translated strings in french.
Refreshed with "make update-po".
---
po/de.po| 11 +++
p
>From 3f029b3549b736f57cfb73c016022f13185187f8 Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Mon, 26 Jan 2015 17:12:54 +0100
Subject: [PATCH 5/9] Translate fsckd messages for plymouth
For plymouth themes not supporting i18n (like .script), send translated
messages to display to user, which
>From 20b16b76f4197604525579cef99c8d6b8b5484e5 Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Mon, 26 Jan 2015 17:30:00 +0100
Subject: [PATCH 7/9] Add fsckd service and socket, retarget systemd-fsck
systemd-fsckd can be socket-activated by systemd-fsck process. Reflect that
in the different
Le 18/02/2015 00:30, Zbigniew Jędrzejewski-Szmek a écrit :
On Tue, Feb 17, 2015 at 05:26:05PM +0100, Didier Roche wrote:
+r = send_message_plymouth_socket(m->plymouth_fd,
plymouth_cancel_message, false);
+if (r < 0)
+log_warning_errno(r, "
>From 9227f9a919084f937fd29856935016e0ee9e754e Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Thu, 29 Jan 2015 16:12:58 +0100
Subject: [PATCH 4/9] Add gettext support
---
configure.ac | 1 +
src/shared/util.c | 8
src/shared/util.h | 2 ++
3 files changed, 11 insertions(+)
di
>From 6006bedd30530a91c2dee7e3822a8840799752e4 Mon Sep 17 00:00:00 2001
From: Didier Roche
Date: Mon, 26 Jan 2015 16:01:11 +0100
Subject: [PATCH 2/9] systemd-fsck: always connect to systemd-fsckd
Remove the plymouth running or show-status checks from systemd-fsck. Instead,
always connect to sys
Hey,
Martin, while distro-patching ubuntu based on 219 told me that the
patches didn't apply cleanly anymore (some po, man pages and strappenda
-> strjoina changes). I did rebase on latest master then and repost here
the whole set of patches.
Also, we did notice that plymouth (at boot) and p
2015-02-18 12:19 GMT+02:00 Lennart Poettering :
> On Wed, 18.02.15 12:13, Joonas Sarajärvi (m...@iki.fi) wrote:
>
>> 2015-02-18 12:07 GMT+02:00 Lennart Poettering :
>> > On Wed, 18.02.15 06:22, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>>
>> >>
>> >> btrfs checksumming theoretically allows you
On Wed, 18.02.15 12:13, Joonas Sarajärvi (m...@iki.fi) wrote:
> 2015-02-18 12:07 GMT+02:00 Lennart Poettering :
> > On Wed, 18.02.15 06:22, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> >>
> >> btrfs checksumming theoretically allows you to transparently recover
> >> after media corruption if
2015-02-18 12:07 GMT+02:00 Lennart Poettering :
> On Wed, 18.02.15 06:22, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>>
>> btrfs checksumming theoretically allows you to transparently recover
>> after media corruption if filesystem has redundancy (more than one copy
>> of data). Journald checks
On Tue, 17.02.15 17:35, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
Please fix this for all arguments, not just symlinks.
> diff --git a/src/tmpfiles/tmpfiles.c b/src/tmpfiles/tmpfiles.c
> index c948d4d..1b35b8e 100644
> --- a/src/tmpfiles/tmpfiles.c
> +++ b/src/tmpfiles/tmpfiles.c
> @@
On Wed, 18.02.15 06:22, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> В Wed, 18 Feb 2015 01:14:44 +0100
> Zbigniew Jędrzejewski-Szmek пишет:
>
> > On Tue, Feb 17, 2015 at 08:05:29PM +0100, Goffredo Baroncelli wrote:
> > > Hi Lennart,
> > >
> > > On 2015-02-16 23:59, Lennart Poettering wrote:
On Tue, 17.02.15 20:05, Goffredo Baroncelli (kreij...@libero.it) wrote:
> Hi Lennart,
>
> On 2015-02-16 23:59, Lennart Poettering wrote:
> > * journald now sets the special FS_NOCOW file flag for its
> > journal files. This should improve performance on btrfs, by
> > a
On Tue, 17.02.15 23:30, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> Lennart Poettering wrote on 17/02/15 10:08:
> >> > mount something-else /foo
> >> > systemctl start foo.mount
> > In this case the second line is a NOP, since the first line already
> > mounted something on /foo, and thus made f
On Tue, 17.02.15 20:24, Luke Kenneth Casson Leighton (l...@lkcl.net) wrote:
> i note that there was announcement recently that the systemd team
> 'listens to users', so i am taking you at your word on that.
Hmm, I am not aware of such an "announcement". I generally listen
though, but I don't alw
Hi there
---
I am running a fedora21 box that acts as a libvirt host for lxc containers
guests
This is based on vanilla fedora (maybe a little bit behind by a few weeks) and
a locally rebuild libvirt based on 1.2.11
root@bigjohn /var/log # uname -a
Linux bigjohn.pl.sophia.inria.fr 3.18.3-201
Hi Andrei,
> This means if link was administratively down it will be reactivated again
>
> ip link set dev down-link down
> unplug up-link
> plug up-link
>
> down-link is now up. Is it intentional?
At the time you issue "plug up-link" you don't know if the down-link is down
due to " ip link se
Hi Luke,
I am mostly a lurker on the systemd mailing list, so my opinion does
not carry weight in this community.
On Tue, Feb 17, 2015 at 9:24 PM, Luke Kenneth Casson Leighton
wrote:> so i'm not going to "protest" - i'm going to
try a different approach.
> i'd like you to look at this list of de
69 matches
Mail list logo
