I am using systemd, journald and systemd-coredump in my system. When a
process crashes the systemd-coredump util handles the core dump and logs a
message in the journal with MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1
Now I want to add a routine which will do post crash activities, For eg.,
blink
On Fri, Apr 01, 2016 at 09:32:16PM +0200, Lennart Poettering wrote:
> On Mon, 21.03.16 11:02, Han Pingtian (ha...@linux.vnet.ibm.com) wrote:
>
> > % cat /etc/systemd/system/reproducer.service
> > [Unit]
> > Description=Reproducer of systemd services killed by pids
> > After=multi-user.target
> >
It seems that systemd-run does not start the process in the specified slice
when starting a transient scope instead of a service.
I have created a test.slice, and started it:
# systemctl status test.slice
● test.slice - Test slice
Loaded: loaded (/usr/lib/systemd/system/t
Hi,
I have been running some provocative tests on a systemd based OS with Clould99
and I have found
out that systemd-networkd daemon would not recover after killing it with
SIGTERM. This is quite
understandable since the systemd-networkd.service is configured with
"Restart=on-failure".
Is that
On 04/05/2016 08:40 AM, Lennart Poettering wrote:
one day of hands-on
training sessions.
Who will be training what exactly?
JBG
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/system
Heya!
We are happy to announce the 2016 installment of systemd.conf, the
conference of the systemd project!
After our successful first conference 2015 we’d like to repeat the
event in 2016 for the second time. The conference will take place on
September 28th until October 1st, 2016 at betahaus in
