It has the same possible values as StartLimitAction= and is executed
immediately if a service fails.
---
Hi Lennart,
Something like this maybe? I'm not quite sure about the condition in
service_enter_dead(). I don't think the action should be executed when the
service is explicitly stopped.
On 03/26/2014 09:02 AM, Michael Olbrich wrote:
It has the same possible values as StartLimitAction= and is executed
immediately if a service fails.
---
Hi Lennart,
Something like this maybe? I'm not quite sure about the condition in
service_enter_dead(). I don't think the action should be
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
On 25 March 2014 18:01, Kai Hendry hen...@webconverger.com wrote:
Requires=dev-input-by\x2did-usb\x2d13ba_0001\x2devent\x2dkbd.device
On #systemd IRC I was recommended After=, and I think it's working as it
should!
On Wed, Mar 26, 2014 at 10:19:53AM +, Jóhann B. Guðmundsson wrote:
On 03/26/2014 09:02 AM, Michael Olbrich wrote:
It has the same possible values as StartLimitAction= and is executed
immediately if a service fails.
---
Hi Lennart,
Something like this maybe? I'm not quite sure about
---
src/libsystemd/sd-resolve/test-resolve.c | 48 +++-
1 file changed, 22 insertions(+), 26 deletions(-)
diff --git a/src/libsystemd/sd-resolve/test-resolve.c
b/src/libsystemd/sd-resolve/test-resolve.c
index d3b2d55..6334dad 100644
---
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not present, I'd
probably start it via a udev rule and SYSTEMD_WANTS.
Do you have an
On 03/26/2014 01:50 PM, Kai Hendry wrote:
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not present, I'd
probably start it via a
On 2014-03-26 14:50, Kai Hendry wrote:
Thanks Michael for answering, :)
On 26 March 2014 18:59, Michael Biebl mbi...@gmail.com wrote:
2014-03-26 3:56 GMT+01:00 Kai Hendry hen...@webconverger.com:
If your daemon is not functional if the hardware is not present, I'd
probably start it via a udev
Add hwdb entry for Samsung Series 7 Ultra.
---
hwdb/60-keyboard.hwdb | 8
1 file changed, 8 insertions(+)
diff --git a/hwdb/60-keyboard.hwdb b/hwdb/60-keyboard.hwdb
index bd8fd10..832c686 100644
--- a/hwdb/60-keyboard.hwdb
+++ b/hwdb/60-keyboard.hwdb
@@ -924,6 +924,14 @@
On Wed, Mar 26, 2014 at 06:48:13PM -0700, Scott Thrasher wrote:
Add hwdb entry for Samsung Series 7 Ultra.
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
There is an interesting bug which can be used to crash systemd via a
dangling symlink. For details please see [0].
To trigger the bug, you need a socket activated service. I'm using
cups in this case.
The steps to reproduce are
a/ Make sure cups.socket is properly configured and in state active
11 matches
Mail list logo
