I know everyone here is super busy, but I just wanted to bump this a
sec before letting it die to make sure it didn't just get lost or
something. (If someone agrees that it should be a feature, I'd happily
try to work on it.)
On Tue, Mar 20, 2018 at 4:08 PM, Ryan Gonzalez wrote:
Hello!!
Rec
After running a bunch of systemd-nspawn containers, I am left with a few that
seem to be empty, running nothing, but refuse to die or be killed after they
did their useful work (so they did run correctly, the problem seems to occur on
poweroff). What might be going on here?
This is:
* x86_64
*
On Fr, 23.03.18 12:52, Filipe Brandenburger (filbran...@google.com) wrote:
> Hi!
>
> So I'm testing a program repeatedly and using `systemd-run` to start a
> service with it, passing it a specific unit name.
>
> When the test finishes and I bring down the service, I want to be able to
> collect
Hi!
So I'm testing a program repeatedly and using `systemd-run` to start a
service with it, passing it a specific unit name.
When the test finishes and I bring down the service, I want to be able to
collect the journald logs for that execution of the test alone.
Right now what I'm doing is namin
On Fri, Mar 23, 2018 at 5:41 PM, Brian J. Murrell
wrote:
> If I have:
>
> Wants=system.slice nss-lookup.target named-setup-rndc.service
>
> in named-pkcs11.service, so shouldn't mean that named-pkcs11.service
> will be started up before the nss-lookup.target is Reached/Started?
>
No, dependencie
If I have:
Wants=system.slice nss-lookup.target named-setup-rndc.service
in named-pkcs11.service, so shouldn't mean that named-pkcs11.service
will be started up before the nss-lookup.target is Reached/Started?
That doesn't seem to be the case on my system:
Mar 23 09:44:03 server.interlinx.bc.ca
