Comment 7 for bug 1452205

I don't think these configs should be the same. When pluto is running. Pluto.pid file will be created.
In my environment (OpenStack: kilo applied libreswan patch. OS: rhel7) when using libreswan, all worked well.

[root@test100 run]# ps -ef | grep ipsec
root 18198 1 0 17:15 ? 00:00:00 /usr/libexec/ipsec/pluto --ctlbase /var/lib/neutron/ipsec/86243bc0-9bfc-401e-9371-43da6e5a1d6b/var/run/pluto --ipsecdir /var/lib/neutron/ipsec/86243bc0-9bfc-401e-9371-43da6e5a1d6b/etc --use-netkey --uniqueids --nat_traversal --secretsfile /var/lib/neutron/ipsec/86243bc0-9bfc-401e-9371-43da6e5a1d6b/etc/ipsec.secrets --virtual_private %v4:192.168.1.0/24,%v4:172.16.100.0/24
root 18774 23739 0 17:19 pts/1 00:00:00 grep --color=auto ipsec
[root@test100 run]# pwd
/var/lib/neutron/ipsec/86243bc0-9bfc-401e-9371-43da6e5a1d6b/var/run
[root@test100 run]# ls
pluto pluto.ctl pluto.pid

There's some doc about pluto.pid and pluto can be found in http://www.freeswan.org/freeswan_trees/CURRENT-TREE/doc/manpage.d/ipsec_pluto.8.html.