[Swan] Cannot start ipsec service using systemd

[Philippe Vouters]

Dear Elison,

I do thank very much to keep us informed. I am a bit surprised by what 
you found. On my Fedora 17 computer, I have the following:
[philippe at victor libreswan]$ ls -l /
...
lrwxrwxrwx.   1 root root      7 Jun  2  2012 bin -> usr/bin
...
I now can't certify it. However I believe it has always been like that.

Yours truly,

Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/
SIP: sip:Vouters at sip.linphone.org

Le 09/01/2013 08:28, Elison Niven a écrit :
> Hi,
>
> Found the culprit. My systemd unit file had this line :
> ExecStart=/usr/bin/sh -c 'eval `/usr/local/libexec/ipsec/pluto 
> --config /etc/ipsec.conf --nofork $PLUTO_OPTIONS`'
>
> But in Fedora 16 :
> # which sh
> /bin/sh
>
> Therefore it was only required to change it to :
> ExecStart=/bin/sh -c 'eval `/usr/local/libexec/ipsec/pluto --config 
> /etc/ipsec.conf --nofork $PLUTO_OPTIONS`'
>
> Thanks !
>
> On Friday 04 January 2013 08:49:40 PM IST, Philippe Vouters wrote:
>> Paul,
>>
>> Pluto should NOT be running as per Elison's ipsec verify output
>>
>> Philippe Vouters (Fontainebleau/France)
>> URL: http://vouters.dyndns.org/
>> SIP: sip:Vouters at sip.linphone.org
>>
>> Le 04/01/2013 16:16, Paul Wouters a écrit :
>>> On Fri, 4 Jan 2013, Elison Niven wrote:
>>>
>>> Why is it that "stop" is failing? Was there perhaps an openswan pluto
>>> running instead of a libreswan pluto, which confused "whack"?
>>>
>>> Can you "killall -9 pluto" and then run "systemctl start
>>> ipsec.service" ?
>>>
>>> Paul
>>> _______________________________________________
>>> Swan mailing list
>>> Swan at lists.libreswan.org
>>> https://lists.libreswan.org/mailman/listinfo/swan
>>>
>>
>>
>>
>
> -- 
> Best Regards,
> Elison Niven
>
>