On Wed, 28 Sep 2011 23:01:46 +0200 Reindl Harald wrote:
> thank you for your reply
>
> first i tried two services (netatalk.service + netatalk-cnid.service)
> but for whatever reason /usr/sbin/cnid_metad will be started with
> a correct zero-return-value but the process is closed, tried
> preforki
thank you for your reply
first i tried two services (netatalk.service + netatalk-cnid.service)
but for whatever reason /usr/sbin/cnid_metad will be started with
a correct zero-return-value but the process is closed, tried preforking/simple
the other "problem" is that i want take away complexity f
On Wed, 28 Sep 2011 17:49:54 +0200 Reindl Harald wrote:
> why does systemd not restart a killed service if the
> "ExecStartPre"-process is still running, see below - at my opinion
> after "killall afpd" the service should be restarted and in a perfect
> case even if "ExecStartPre"-process dies
>
>
Hello
On Wed, Sep 28, 2011 at 6:59 PM, Michael Olbrich
wrote:
> How to implement this is systemd:
> systemd already has the concept of a state for each service and a very
> simple method (sd_notify) for the service to provide status information to
> systemd.
> This is implemented in the first pat
hat is generated
> > then. If you find nothing useful in it, please paste it somewhere so
> > that I can have a look.
>
> Nothing jumps out at me so I'd like to take you up on that offer :)
> http://dev.laptop.org/~dsd/20110928/systemd-debug-shutdown-hang.txt
>
what
---
src/dbus-manager.c |4
src/manager.c | 20
src/manager.h |3 +++
src/service.c |2 ++
4 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/src/dbus-manager.c b/src/dbus-manager.c
index 7b68156..2254ec8 100644
--- a/src/dbus-mana
---
Makefile.am| 21 ++-
src/99-systemd.rules.in|2 +
src/watchdogd.c| 119
units/systemd-watchdogd.service.in | 16 +
4 files changed, 156 insertions(+), 2 deletions(-)
create mode 10064
---
src/dbus-service.c |4
src/load-fragment-gperf.gperf.m4 |2 ++
src/service.c| 27 +++
src/service.h|4
4 files changed, 37 insertions(+), 0 deletions(-)
diff --git a/src/dbus-service.c b/src/
---
src/dbus-service.c |4
src/service.c | 20
src/service.h |2 ++
3 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/src/dbus-service.c b/src/dbus-service.c
index 3486623..5a740de 100644
--- a/src/dbus-service.c
+++ b/src/dbus-service.c
Hi,
I've been playing with some ideas on how to add watchdog support to
systemd. I don't like talking about vaporware so here are some patches with
a prototype implementation. It should give you an idea on how this could be
done.
A few words on the ideas behind this: When working with a watchdog
hi
why does systemd not restart a killed service if the "ExecStartPre"-process is
still running, see below - at my opinion after "killall afpd" the service
should be restarted and in a perfect case even if "ExecStartPre"-process dies
systemd-26-10.fc15.x86_64
___
[root@te
On Thu, 29.09.11 00:16, Nick Urbanik ([email protected]) wrote:
> Dear Folks,
>
> I am running Fedora 15 on a 4-core x86_64 machine which received a
> power surge recently, and spontaneously rebooted. Strange behaviour
> followed, so I touched /forcefsck and /.autorelabel on separate
> occasions,
output that is generated
> > then. If you find nothing useful in it, please paste it somewhere so
> > that I can have a look.
>
> Nothing jumps out at me so I'd like to take you up on that offer :)
> http://dev.laptop.org/~dsd/20110928/systemd-debug-shutdown-hang.txt
Hmm
Dear Folks,
I am running Fedora 15 on a 4-core x86_64 machine which received a
power surge recently, and spontaneously rebooted. Strange behaviour
followed, so I touched /forcefsck and /.autorelabel on separate
occasions, rebooting each time. I observe the following behaviour
regardless of whet
ewhere so
> that I can have a look.
Nothing jumps out at me so I'd like to take you up on that offer :)
http://dev.laptop.org/~dsd/20110928/systemd-debug-shutdown-hang.txt
Thanks,
Daniel
___
systemd-devel mailing list
[email protected]
15 matches
Mail list logo
