With Strongswan 5.1.2-0ubuntu8 on Ubuntu Xenial, things have improved
slightly. systemd will notice if one runs "ipsec stop". Previously,
upstart was unable to figure it out and would re-spawn the service.

One problem remains with systemd: If you "ipsec start" while the systemd
service is not running, the resulting daemons will not be tracked by
systemd.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1287339

Title:
  Using "ipsec start|stop" confuses upstart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1287339/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to