Hi Martin, On Fri, Mar 27, 2015 at 04:40:25PM +0100, Martin Pitt wrote: > > If so, a mere "ipsec stop" after that should be able to crash > > systemd. > > Not that, it just marks the unit as stopped but keeps the processes > running. But killing the two daemons manually makes the cgroup empty > and I get that very exception.
I *think* you read "systemctl stop ipsec" while I really meant "ipsec stop" (ipsec being /usr/sbin/ipsec, and "stop" being an action that sends SIGTERM to the daemons, among other things). By "get that very exception" you mean that systemd crashes for you as well? If so, that's great :) Anything more I can do to help then? You seem to be in a better position to reproduce than me at the moment. On a side note, I've noticed that if I put the system under "stress --cpu 8" the behavior changes and "systemctl restart strongswan" works properly. This definitely points to some kind of race. Thanks! Faidon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
