[systemd-devel] [PATCHv4] core: notify triggered by socket of a service

2013-07-22 Thread Umut Tezduyar
--- TODO |3 --- src/core/service.c | 31 --- src/core/socket.c | 39 ++- src/core/socket.h |3 --- 4 files changed, 38 insertions(+), 38 deletions(-) diff --git a/TODO b/TODO index ba8bb8e..e0c4857

Re: [systemd-devel] [PATCHv3] core: notify triggered by socket of a service

2013-07-22 Thread Umut Tezduyar
On Thu, Jul 18, 2013 at 8:11 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 18.07.13 15:27, Umut Tezduyar (u...@tezduyar.com) wrote: +static void socket_trigger_notify(Unit *u, Unit *other) { +Socket *s = SOCKET(u); +Service *se = SERVICE(other); + +

[systemd-devel] [PATCH] NEWS: fix mistake

2013-07-22 Thread Maciej Wereski
--- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index d44e6fe..8f81ec1 100644 --- a/NEWS +++ b/NEWS @@ -11,7 +11,7 @@ CHANGES WITH 206: * systemctl now supports filtering the unit list output by load state, active state and sub state,

Re: [systemd-devel] [PATCH 2/2] vconsole-setup: setup negative conditional on uml

2013-07-22 Thread Ramkumar Ramachandra
Lennart Poettering wrote: So please, ask the UML guys to somehow cleanup their VT mess. It's their broken code, and their job to fix it. The question is how? Just tell me what to do, and I'll do it myself. I can understand if you are disappointed by this, but please try to see it from out

Re: [systemd-devel] /etc/systemd/system/darkice.service

2013-07-22 Thread Kai Hendry
On 19 July 2013 01:29, Lennart Poettering lenn...@poettering.net wrote: It is certainly surprising at first, but it makes a lot of sense. In systemd ordering deps and requirement deps are truly orthogonal. This is useful in many cases, because sometimes you just want to pull something else in,

Re: [systemd-devel] [PATCH 2/2] vconsole-setup: setup negative conditional on uml

2013-07-22 Thread Ramkumar Ramachandra
Ramkumar Ramachandra wrote: Got it. So, it should have provided /dev/tum* (or something) instead of /dev/tty*. But what can we do about it now? I certainly cannot remove /dev/tty* and murder the users. Wait, I think I have an idea to preserve backward compatibility. I'll remove the

[systemd-devel] Excluding .hwdb files

2013-07-22 Thread Umut Tezduyar
Hi, For an embedded system that is not using hwdb.bin, we are shipping roughly 4 mb .hwdb files under /usr/lib/udev/hwdb.d. Is it distributions responsibility to clean up .hwdb files after build or should we have a configure option to exclude hwdb support? Thanks, Umut

Re: [systemd-devel] Excluding .hwdb files

2013-07-22 Thread Kay Sievers
On Mon, Jul 22, 2013 at 3:32 PM, Umut Tezduyar u...@tezduyar.com wrote: For an embedded system that is not using hwdb.bin, we are shipping roughly 4 mb .hwdb files under /usr/lib/udev/hwdb.d. Is it distributions responsibility to clean up .hwdb files after build or should we have a configure

[systemd-devel] [PATCHv3] tmpfiles, man: Add xattr support to tmpfiles

2013-07-22 Thread Maciej Wereski
This patch makes it possible to set extended attributes on files created by tmpfiles. This can be especially used to set SMACK security labels on volatile files and directories. It is done by adding new line of type t. Such line should contain attributes in Argument field, using following format:

Re: [systemd-devel] /etc/systemd/system/darkice.service

2013-07-22 Thread Andrey Borzenkov
В Mon, 22 Jul 2013 17:48:11 +0800 Kai Hendry hen...@iki.fi пишет: I enabled the above as pingtest.service and added Wants=network-online.target under the [Unit] heading in darkice.service. Still I don't understand how pingtest.service can fail here with exit 2 and even more confusingly

Re: [systemd-devel] Excluding .hwdb files

2013-07-22 Thread Michael Biebl
2013/7/22 Kay Sievers k...@vrfy.org: On Mon, Jul 22, 2013 at 3:32 PM, Umut Tezduyar u...@tezduyar.com wrote: For an embedded system that is not using hwdb.bin, we are shipping roughly 4 mb .hwdb files under /usr/lib/udev/hwdb.d. Is it distributions responsibility to clean up .hwdb files after

Re: [systemd-devel] Excluding .hwdb files

2013-07-22 Thread Tom Gundersen
On 22 Jul 2013 18:19, Michael Biebl mbi...@gmail.com wrote: 2013/7/22 Kay Sievers k...@vrfy.org: On Mon, Jul 22, 2013 at 3:32 PM, Umut Tezduyar u...@tezduyar.com wrote: For an embedded system that is not using hwdb.bin, we are shipping roughly 4 mb .hwdb files under /usr/lib/udev/hwdb.d.

Re: [systemd-devel] Excluding .hwdb files

2013-07-22 Thread Kay Sievers
On Mon, Jul 22, 2013 at 6:18 PM, Michael Biebl mbi...@gmail.com wrote: 2013/7/22 Kay Sievers k...@vrfy.org: On Mon, Jul 22, 2013 at 3:32 PM, Umut Tezduyar u...@tezduyar.com wrote: For an embedded system that is not using hwdb.bin, we are shipping roughly 4 mb .hwdb files under

Re: [systemd-devel] [PATCH 2/2] vconsole-setup: setup negative conditional on uml

2013-07-22 Thread Lennart Poettering
On Mon, 22.07.13 13:31, Ramkumar Ramachandra (artag...@gmail.com) wrote: Lennart Poettering wrote: They can call their ttys any way they want. If the call them /dev/tty[1..64] however, then they need to implement the VC interfaces. All of them. Also note that some hypervisors

Re: [systemd-devel] removal of RD_TIMESTAMP support in initrd

2013-07-22 Thread Lennart Poettering
On Fri, 19.07.13 22:02, Dave Reisner (d...@falconindy.com) wrote: Hi, With systemd 206 near release, I'd like to understand if commit c72aadd1851096ea is going to stand. This commit removes support for reading RD_TIMESTAMP in the initramfs, and thus makes systemd mandatory for measuring

Re: [systemd-devel] [PATCH] NEWS: fix mistake

2013-07-22 Thread Lennart Poettering
On Mon, 22.07.13 11:02, Maciej Wereski (m.were...@partner.samsung.com) wrote: --- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index d44e6fe..8f81ec1 100644 --- a/NEWS +++ b/NEWS @@ -11,7 +11,7 @@ CHANGES WITH 206: * systemctl now

Re: [systemd-devel] removal of RD_TIMESTAMP support in initrd

2013-07-22 Thread Tom Gundersen
On Tue, Jul 23, 2013 at 12:44 AM, Lennart Poettering lenn...@poettering.net wrote: I do understand that you are currently not running systemd in the initrd [1], so for you for now this is indeed a loss of functionality. I am sorry for that, but please understand this as gentle push to maybe use