Zbigniew Jędrzejewski-Szmek writes:
> Hi,
> I've hit a bit of a problem with nsenter and systemd-nspawn.
> When nsenter is used to enter the PID namespace created with
> systemd-nspawn, and the container's init attempts a shutdown,
> it hangs because nsenter is suspended.
>
> The sequence of even
Hi,
I've hit a bit of a problem with nsenter and systemd-nspawn.
When nsenter is used to enter the PID namespace created with
systemd-nspawn, and the container's init attempts a shutdown,
it hangs because nsenter is suspended.
The sequence of events leading to the hang is:
1. nsenter launches a s
On Fri, Apr 19, 2013 at 11:13 PM, Josh Triplett wrote:
> ---
>
> Resubmitting the uncontroversial bits.
Applied.
Thanks,
Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Op 18 apr. 2013, om 19:18 heeft George McCollister
het volgende geschreven:
> On 04/10/2013 12:03 PM, Koen Kooi wrote:
>> Hi,
>>
>> I have a bit of a heisenbug where dropbear.socket will just die and needs a
>> systemctl restart dropbear.socket. I can't tell why it's dying, just that it
>> d
В Fri, 19 Apr 2013 22:01:41 -0700
Peter Li пишет:
> On 04/19/2013 04:16 AM, Colin Guthrie wrote:
>
> >> When I then run `systemctl start wsgw; systemctl status wsgw` I get:
> >>
> >> wsgw.service - WebSockets Gateway for pianod
> >>Loaded: loaded (/usr/lib/systemd/system/wsgw.se
