[strongSwan] Strongswan 4.5.1 Sqlite database not updated until ipsec is restarted

[CETIAD - Fabrice Barconnière]

Hi Martin,

The problem is our tool erases database file and generates a new 
database file each time we validate a configuration change.
I've fixed this bug in our tool and it's ok now.

I wonder if a new fonctionnality could be added in StrongSwan.
ipsec reload could close database and open the new file handler.
Do you think it is possible ?

Thanks and regards,
Fabrice

Le 21/09/2011 16:53, CETIAD - Fabrice Barconnière a écrit :
>
> Le 21/09/2011 16:29, Martin Willi a écrit :
>>> Is there a way to reload or reread database or flush database cache
>>> without restarting ipsec ?
>> Connection definitions shown in "statusall" and IKE connections that get
>> newly established are always reread from the database. If it doesn't
>> show up in "statusall", it is either invalid or something is wrong with
>> your database.
>>
>>> I've executed these commands before ipsec up with no success:
>>> ipsec update
>>> ipsec reload
>>> ipsec update
>>> ipsec purgeike
>> It works fine here, any changes in the database are directly visible in
>> statusall. Does the changed connection show up after you restart the
>> daemon?
> Yes. After ipsec restart, connections show up.
>
>> What is your SQLite version?
> Version 3
> Database generated with python-sqlalchemy 0.5.8-1
> libsqlite3-0        3.6.22-1 installed on server.
>
>> Regards
>> Martin
>>
> Regards
> Fabrice
>
> _______________________________________________
> Users mailing list
> Users at lists.strongswan.org
> https://lists.strongswan.org/mailman/listinfo/users