the fix 5d6ff678ea0, would it fix all initsystems or only systemd?
It is still showing up upstart and other inits unconditionally. I had to 
disable manually.

-antony

On Fri, Apr 06, 2018 at 08:11:34AM -0400, Paul Wouters wrote:
> On Thu, 5 Apr 2018, Antony Antony wrote:
> 
> > "ipsec start" fails on debian. It seems systemd/ipsec.service fails.
> > 
> > the python dependencies should be ideally optional build option. think of 
> > embedded systems without python...
> > 
> > and definately not hard coding to python2.
> > 
> > journalctl -xe
> > 
> > Apr 05 13:31:03 swanbase systemd[10604]: ipsec.service: Failed to execute 
> > command: No such file or directory
> > Apr 05 13:31:03 swanbase systemd[10604]: ipsec.service: Failed at step EXEC 
> > spawning /usr/lib/ipsec/portexcludes: No such file or di
> > -- Subject: Process /usr/lib/ipsec/portexcludes could not be executed
> > -- Defined-By: systemd
> 
> I've introduced USE_PORTEXCLUDES= and disabled it per default.
> 
> I also do not like the fact it would introduce a python dependancy.
> I suspect we would not have many users that want to enable this feature.
> 
> Paul
_______________________________________________
Swan-dev mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-dev

Reply via email to