On 04/02/12 10:04, Warpme wrote:
On 2/1/12 8:37 PM, Chris Paulson-Ellis wrote:
On 01/02/12 19:07, Lennart Poettering wrote:
On Wed, 01.02.12 18:54, Chris Paulson-Ellis ([email protected]) wrote:
Is there some way to get the client to always restart when server
restarts, for whatever reason
The reaping of generator processes run as part of a daemon-reload should not
call waitid(PID_ALL). The waitid() call in execute_directory() is intended only
to reap the executed processes, but if a service process exits at about the
same time as a daemon-reload, then that service process is reaped
On 01/02/12 19:26, Lennart Poettering wrote:
On Wed, 01.02.12 19:13, Chris Paulson-Ellis ([email protected]) wrote:
On 01/02/12 19:07, Lennart Poettering wrote:
On Wed, 01.02.12 18:54, Chris Paulson-Ellis ([email protected]) wrote:
Is there some way to get the client to always restart when
On 01/02/12 19:05, Lennart Poettering wrote:
(As I figured out newer Intel chipsets all have watchdogs now, so I am
actually quite keen to see this implemented in systemd now, since I can
actually test it.)
Just a warning to anyone who's thinking of depending on the chipset
watchdog... In my e
On 01/02/12 19:07, Lennart Poettering wrote:
On Wed, 01.02.12 18:54, Chris Paulson-Ellis ([email protected]) wrote:
Is there some way to get the client to always restart when server
restarts, for whatever reason?
No, there isn't. But what you describe is something I consider a bug,
and t
I've got a client service (client.service) that requires a server
service (server.service). They are weakly coupled by a polling http
protocol, but the client needs to restart when server does or it can get
into trouble in it's state machine (and can't easily be re-coded to cope).
If I use Req
I'm having trouble getting my head round how hotplugged device
activation should work with systemctl enable/disable.
I have a udev rule that uses ENV{SYSTEMD_WANTS}="foo@%k.service" to hook
device hotplug to systemd and a template unit file for [email protected] that
uses BindTo=dev-%i.device to en
Hi,
I'm running a Java JVM service using:
ExecStart=/usr/bin/java -jar foo.jar
When I stop the service with systemctl, it goes into the failed state
because the JVM exits with status 143 instead of 0.
There doesn't seem to be any way to get a JVM to exit(0) on SIGTERM. You
can run code on t
