<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for the quick response, Francis!</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I don’t plan on running the kea-lac directly, unless as a last resort. But just wanted to confirm my understanding.</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I’ll wait for the kea-lfc-start to be generally available on stable, in the meantime is there any downside to setting lfc-interval to say, 10 minutes?</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Diogo</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="mail-editor-reference-message-container">
<div class="ms-outlook-mobile-reference-message skipProofing">
<meta name="Generator" content="Microsoft Exchange Server">
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>Francis Dupont <fdupont@isc.org><br>
<b>Date: </b>Wednesday, December 10, 2025 at 10:22 AM<br>
<b>To: </b>Kea user's list <kea-users@lists.isc.org><br>
<b>Cc: </b>Diogo André de Assumpção <daa@meta.com><br>
<b>Subject: </b>Re: [Kea-users] LFC Questions<br>
<br>
</div>
<div class="PlainText" style="font-size: 11pt;"><br>
<br>
Diogo André de Assumpção via Kea-users writes:<br>
> Back with some questions, this time around the LFC process.<br>
><br>
> We use a memfile backend and one requirement we have is to refresh the conf=<br>
> ig quite frequently, every 30min right now but looking to reduce that.<br>
><br>
> I believe that by reloading the config either via a service restart or via =<br>
> a =93config-reload=94 command, the LFC process will not run if our =93reloa=<br>
> d config timer=94 < =93lfc-interval=94 set in Kea=92s config.<br>
<br>
=> first it is a very bad idea to run lfc directly so we added a command<br>
to have Kea to call the lfc itself (kea-lfc-start).<br>
<br>
> Is it correct to say that the "lfc-interval=94 time, is based in the =93rel=<br>
> oad=94 time instead of =93uptime=94, as in seen in the result of a =93stat=<br>
> us-get=94 command?<br>
<br>
=> the lfc-interval is run since the last time it was called, and the timer<br>
is reset during reload (warm start). The uptime is from the cold start i.e.<br>
when the server was launched. There is an exception to this: if the lease<br>
file uses a previous version of CSV lfc is immediately called to convert<br>
to the current/last version.<br>
<br>
> My second question is related to the =93kea-lfc=94 cli. Running it directly=<br>
> wouldn=92t affect the running service, right? In other words, it would not=<br>
> replace the =93current=94 file that Kea uses to preserve the memfile=92s c=<br>
> ontents?<br>
<br>
=> Kea opens a lease file and write into it. You can move it and<br>
even remove it and it will continue to write in it (of course when<br>
it is removed you have no access to it through the file system) until<br>
the lfc timer expire, it moves files and opens a new file. the role of<br>
the lfc is to compress the lease history so it is preserved for Kea<br>
warm or cold (re)start without filling the file system.<br>
<br>
Regards<br>
<br>
Francis Dupont <fdupont@isc.org><br>
<br>
PS: there are some commands to recover from disasters as removing the<br>
lease file by accident...<br>
</div>
</div>
</body>
</html>