On Sun, Aug 16, 2015 at 9:29 AM, Lennart Poettering
wrote:
> Could you file a github RFE issue, asking for support for watchdog
> keep-alive message send stuff in PID 1 and nspawn, and watchdog
> keep-alive message receive stuff in nspawn? I think it would make a
> lot of sense to add this!
https
On Fri, Aug 14, 2015 at 1:30 PM, Lennart Poettering
wrote:
> On Mon, 10.08.15 08:03, Rich Freeman (r-syst...@thefreemanclan.net) wrote:
>
> We have watchdog (see WatchdogSec= documentation in
> systemd.service(5)) support in all our long-running daemons, and PID 1
> will kill
Occassionally I'll have nspawn containers that freeze up when they're
loading. What is the best way to troubleshoot these and get useful
info to devs?
This is on systemd-218, on Gentoo.
Also, is there any way to detect these freezes, perhaps getting the
service launching it to at least fail? Sh
On Mon, Jul 27, 2015 at 10:51 AM, Lennart Poettering
wrote:
>
> If you are looking for a way to start this service only when an NFS
> mount is attempted, then I must disappoint you: there's currently no
> way to do this nicely, as you can neither express "applies only to
> NFS", nor is there a way
I noticed that mount units for nfs shares created by the generator do
not Want=nfs-client.target or similar.
That means that if you don't explicitly want nfs-client in your
configuration then nfs shares will get mounted, but services like
rpc-statd-notify.service won't run.
Would it make sense to
On Mon, Oct 27, 2014 at 11:32 AM, Lennart Poettering
wrote:
> Network namespaces are relevant for the process that originally binds
> the sockets. In the case of socket-activated containers that would be
> the host. If you then pass the fds into the containers and those are
> locked into their own
On Mon, Oct 27, 2014 at 10:49 AM, Lennart Poettering
wrote:
> In general I think making use of socket notification here would be the
> much better option, as it removes the entire need for ordering things
> here. nspawn already support socket activation just fine. If your
> mysql container would u
One of the useful options in nspawn is the ability to boot the init
within the container using -b, especially if that init happens to be
systemd.
However, I could not find any easy way to set a dependency on a
service within a container.
Example use case:
Unit 1 boots an nspawn container that run
On Sun, Jun 29, 2014 at 10:27 AM, Tom Gundersen wrote:
> On Sat, Jun 28, 2014 at 11:29 AM, Tom Gundersen wrote:
>> Your analysis is correct. networkd is not updating the lft.
>>
>> We should change two things: dracut (or whatever is being used on your
>> machine) should set an infinite lifetime w
I'm running systemd-212 and dracut-037, on a diskless box with an nfs
root and pxe boot.
After a number of updates I noticed that the box would freeze up after
24h uptime - almost exactly. This behavior is the same whether I have
systemd-networkd running or not (it is configured to set up any
int
10 matches
Mail list logo