Hi All,
I am new to Systemd, Need help about understanding some of features of the
systemd.
I am interested in knowing the failure of a service and the exact cause of
it.
Inside the systemd unit file there are options like SuccessExitStatus and
On-failure. In SuccessExitStatus we can specify the
On Sun, Sep 22, 2013 at 09:10:47PM +0800, cee1 wrote:
Let read()/write() report any error/EOF.
This look OK, but can you provide a bit of motivation?
Zbyszek
---
src/shared/util.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/src/shared/util.c
On Thu, Sep 19, 2013 at 05:03:33PM -0500, Zbigniew Jędrzejewski-Szmek wrote:
Also print out unexpected epoll events explictly.
---
Hi,
could you try with the following patch?
Seeing no objections, I pushed the patch :).
Zbyszek
___
systemd-devel
On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
(Of course, journald should not exit under any such circumstances, but
to find that we first need to track down why it does that currently).
Though it might hide problems, shouldn't journald be configured to
automatically be
At Hackers News, someone (seemingly involved with OpenRC) claims that
the systemd API is somehow licensed under the LGPL. Thus making it
impossible for OpenRC to implement the same API.
See https://news.ycombinator.com/item?id=6446700 for the entire comments
and
On Thu, Sep 26, 2013 at 03:52:09PM +0200, Olav Vitters wrote:
At Hackers News, someone (seemingly involved with OpenRC) claims that
the systemd API is somehow licensed under the LGPL. Thus making it
impossible for OpenRC to implement the same API.
See
This avoids a problem when we inherit a non-zero umask from the
initramfs. This would cause /run/systemd to be created with the wrong
mode.
---
src/core/main.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/src/core/main.c b/src/core/main.c
index 72bd542..f532dca
On Thu, Sep 26, 2013 at 2:46 PM, Olav Vitters o...@vitters.nl wrote:
On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
(Of course, journald should not exit under any such circumstances, but
to find that we first need to track down why it does that currently).
Though it might
On Thu, 26.09.13 15:52, Olav Vitters (o...@vitters.nl) wrote:
At Hackers News, someone (seemingly involved with OpenRC) claims that
the systemd API is somehow licensed under the LGPL. Thus making it
impossible for OpenRC to implement the same API.
See
On 2013-09-26 17:11, Lennart Poettering wrote:
And besides that: the glibc headers carry the
word for word identical copyright header (only replacing systemd by
GNU C Library). So if those headers are OK for usage with OpenRC
the
systemd headers should be too.
But, if I understand correctly,
On Thu, Sep 26, 2013 at 05:46:40PM +0100, Adam Spragg wrote:
On 2013-09-26 17:11, Lennart Poettering wrote:
And besides that: the glibc headers carry the
word for word identical copyright header (only replacing systemd by
GNU C Library). So if those headers are OK for usage with OpenRC
the
On Thu, 26.09.13 15:46, Olav Vitters (o...@vitters.nl) wrote:
On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
(Of course, journald should not exit under any such circumstances, but
to find that we first need to track down why it does that currently).
Though it might
On Thu, 26.09.13 10:50, Mike Gilbert (flop...@gentoo.org) wrote:
This avoids a problem when we inherit a non-zero umask from the
initramfs. This would cause /run/systemd to be created with the wrong
mode.
Merged this, but ordered things so that umask() is only invoked at one
place.
---
On Thu, 26.09.13 18:28, abhishek sharma (abhishek.sharm...@gmail.com) wrote:
Hi All,
I am new to Systemd, Need help about understanding some of features of the
systemd.
I am interested in knowing the failure of a service and the exact cause of
it.
Inside the systemd unit file there are
14 matches
Mail list logo
