Hi,
Are ipsec update and sending HUP to charon the same actions?
No, they are not. `ipsec update` sends a SIGHUP to starter, but starter
does currently not forward the signal to charon. So as you noticed, the
latter has to be done manually.
Regards,
Tobias
Hi guys!
Are ipsec update and sending HUP to charon the same actions?
I'm now setting up logging into filelog on strongswan 5.2.1 and noticed
that ipsec update won't rotate file and update logging config and
sending HUP via pkill effectively does.
Have I missed something?
Thanks in
On 2015-03-18 13:21, Tobias Brunner wrote:
Hi,
Are ipsec update and sending HUP to charon the same actions?
No, they are not. `ipsec update` sends a SIGHUP to starter, but
starter
does currently not forward the signal to charon. So as you noticed,
the
latter has to be done manually.
But still ipsec update does reread contents of ipsec.conf, am I right?
Yes, this will cause starter to reread ipsec.conf.
And does sending HUP to charon forces it to reread ipsec.conf or just
the strongswan.conf?
The charon daemon only reads strongswan.conf, and ipsec.conf is only
read by
On 03/18/2015 9:37 AM, Tobias Brunner wrote:
But still ipsec update does reread contents of ipsec.conf, am I right?
Yes, this will cause starter to reread ipsec.conf.
And does sending HUP to charon forces it to reread ipsec.conf or just
the strongswan.conf?
The charon daemon only reads
