Hi t3sserakt, I think there was simply no _need_ expire them from the cache explicitly. Regardless, I would suggest you don't waste the effort, peerinfo will die, I'm moving hello caching into peerstore where the DB has a per-value expiration field already anyway (see my coding from the last two weeks).
So more helpful in this context would be hacking up the missing Postgres, MySQL and heap database backends for peerstore :-). Happy hacking! Christian On 11/24/18 1:32 PM, t3sserakt wrote: > Hello *, > > > is there any reason that I see expired hellos, when executing > > > gnunet-peerinfo -g > > > or > > > gnunet-peerinfo -i > > > It looks like the hello cache is not update like the files hellos are > persisted into. > > If there is no reason for that I will fix the update mechanism to > include the cache too. > > > Happy hacking! > > > t3ss > > > > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
