`Before` means that if your service and everything in `Before` (e.g.
shutdown.target) is started at the same time, your service will be started
Before the other, but when all are been stopped, your service will get
Stoped After the other (you can see why you don't want your service stopped
after sh
Hello everybody,
I am DBA and trying to setup systemd service for DB2 V11 fix pack 2a (multiple
instances).
I've spent quite a bit of time on this setup without success so far.
I was able to get "ExecStart" part to work, but system reboot is giving me
troubles.
DB2 crashes since "ExecStop" for s
On Wed, May 16, 2018, at 10:56 AM, Simon McVittie wrote:
>
> Projects like libostree and rpm-ostree might have some useful concepts
> or code for managing immutable, read-only rootfs or /usr deployments,
> since that's what they do: in an ostree-based OS, /usr is an
> atomically-updated immutabl
Hello everyone!
My name is Christian Glombek and I am currently a student participant in
the Google Summer of Code program,
working on Fedora IoT & Project Atomic.
As part of this effort, I was tasked with creating a generic health check
framework using systemd.
We want to use it to determine sys
On Thu, 2018-05-24 at 13:47 +0800, Lee, Chun-Yi wrote:
> Currently the systemd-detect-virt returns exit failure code when it
> detected none state. But actually the none state is still a valid
> state but not a process failed.
>
> This patch changes the logic to return success code when the state
On Do, 24.05.18 13:47, Lee, Chun-Yi (joeyli.ker...@gmail.com) wrote:
> Currently the systemd-detect-virt returns exit failure code when it
> detected none state. But actually the none state is still a valid
> state but not a process failed.
>
> This patch changes the logic to return success code
