Re: [systemd-devel] Adopt processes spawned before /lib/systemd/systemd takes over as PID 1?

2015-04-18 Thread Daniel Mack
On 04/18/2015 05:29 AM, Matt Hoosier wrote: On Fri, Apr 17, 2015 at 3:52 PM, Cristian Rodríguez crrodrig...@opensuse.org mailto:crrodrig...@opensuse.org wrote: Did you watch this presentation ? https://www.youtube.com/watch?v=RFVlbaDqll8 what part of systemd is taking 1.5

[systemd-devel] resolved: Assertion 'n 0' failed

2015-04-18 Thread Kai Krakow
Hello! Sometimes I'm seeing messages like this: [ 5780.379921] systemd-resolved[685]: Assertion 'n 0' failed at /var/tmp/portage/sys-apps/systemd-219- r2/work/systemd-219/src/resolve/resolved-dns-answer.c:28, function dns_answer_new(). Aborting. [ 5780.621865] systemd-resolved[7396]:

Re: [systemd-devel] Problem with intermediate target

2015-04-18 Thread Christoph Pleger
Hello, Why does systemd start this service before /var is mounted, though the service should be executed after remote-fs.target, and remote-fs.target comes after local-fs.target? Because remote-fs.target is not part of initial transaction. And why is this different in my

Re: [systemd-devel] Problem with intermediate target

2015-04-18 Thread Andrei Borzenkov
В Thu, 16 Apr 2015 17:10:57 +0200 Christoph Pleger christoph.ple...@cs.tu-dortmund.de пишет: Hello, I wrote: Sounds like you want to create intermediate.target, change default.target to point at it, boot all the way up to intermediate.target, and at that point isolate or start

[systemd-devel] controlling serial console using a token

2015-04-18 Thread Praveen kumar R
Yes it's a kernel command line arg, it is board specific token introduced to control the serial console. if defined serial console should not be enabled. we have this in place for other system initializing system - sytemV , where depending On Fri, Apr 17, 2015 at 4:24 PM, Lennart Poettering

[systemd-devel] [PATCH 3/3] rules: Enable runtime power management on built-in USB Bluetooth controllers

2015-04-18 Thread Matthew Garrett
From: Matthew Garrett mj...@coreos.com If a Bluetooth controller is built into the machine, it should be safe to enable runtime power management on it. Let's do so. --- Makefile.am | 3 ++- rules/90-usb-bluetooth-pm.rules | 8 2 files changed, 10 insertions(+), 1

[systemd-devel] [PATCH 2/3] rules: Enable runtime device power management on a subset of HDA codecs

2015-04-18 Thread Matthew Garrett
From: Matthew Garrett mj...@coreos.com 4.1 ports HDA codec power management to the standard runtime PM framework, which means we have per-codec control over whether it's enabled or not. We've traditionally left this disabled because on some codecs enabling it causes popping noises on power

[systemd-devel] Enable runtime power management on more hardware

2015-04-18 Thread Matthew Garrett
Modern hardware is very sensitive to peripheral power management state. While the kernel supports runtime PM on a lot of hardware, it's mostly disabled by default due to the risk of it breaking a subset of devices. Let's turn it on on devices where we have reasonable confidence in it working, with

[systemd-devel] [PATCH 1/3] rules: Enable runtime device power management on Intel HDA controllers

2015-04-18 Thread Matthew Garrett
From: Matthew Garrett mj...@coreos.com PCI power management seems to work fine on Intel HDA controllers, so let's turn that on. We can expand this to other vendors based on user feedback. --- Makefile.am | 3 ++- rules/90-hda-controller-pm.rules | 3 +++ 2 files changed, 5

Re: [systemd-devel] [PATCH 1/3] rules: Enable runtime device power management on Intel HDA controllers

2015-04-18 Thread Kay Sievers
On Sat, Apr 18, 2015 at 6:11 PM, Matthew Garrett mj...@srcf.ucam.org wrote: From: Matthew Garrett mj...@coreos.com PCI power management seems to work fine on Intel HDA controllers, so let's turn that on. We can expand this to other vendors based on user feedback. +ACTION==add,

Re: [systemd-devel] [PATCH 1/3] rules: Enable runtime device power management on Intel HDA controllers

2015-04-18 Thread Matthew Garrett
(Resending from the correct address) On Sat, Apr 18, 2015 at 07:51:26PM +0200, Kay Sievers wrote: It looks like an unconditional static assignment. Why should udev carry this? We generally do not want to do things like that. Udev can help if there is conditional policy or complex

[systemd-devel] [PATCH v2] udev: Allow detection of udevadm settle timeout

2015-04-18 Thread Nir Soffer
When udevadm settle times out, it exits with exit code 1. This make it impossible for users to detect a timeout and handle real errors. Now we use exit code 3 on timeouts. --- src/udev/udevadm-settle.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[systemd-devel] [PATCH] udev: Fix ping timeout when settle timeout is 0

2015-04-18 Thread Nir Soffer
When running udevadm settle --timeout=0, the ping always times out, and udevadm will return 0 without checking the queue state. Since zero timeout is considered as unlimited timeout, we use now unlimited ping timeout. --- src/udev/udevadm-settle.c | 4 +++- 1 file changed, 3 insertions(+), 1

[systemd-devel] [PATCH v3 1/2] udev: settle should return immediately when timeout is 0

2015-04-18 Thread Nir Soffer
udevadm manual says: A value of 0 will check if the queue is empty and always return immediately. However, currently we ignore the deadline if the value is 0, and wait without any limit. Zero timeout behaved according to the documentation until commit ead7c62ab7 (udevadm: settle - kill

[systemd-devel] [PATCH v3 2/2] udev: Skip ping if timeout is 0

2015-04-18 Thread Nir Soffer
When running udevadm settle --timeout=0, udev_ctrl_send_ping always times out, and settle returns 0 without checking the queue. Now we skip ping in this case, and return the queue state. --- src/udev/udevadm-settle.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git