Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Message-ID: <rt-4.4.1-98210-1535548688-1102.48110-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Interface: Web
X-RT-Original-Encoding: utf-8
X-Mailer: MIME-tools 5.508 (Entity 5.508)
MIME-Version: 1.0
In-Reply-To: <rt-4.4.1-11120-1535547620-739.48110-0-0@isc.org>
References: <RT-Ticket-48110@isc.org>
 <87zhxdlflq.fsf@pzhukov-workstation.usersys.redhat.com>
 <rt-4.4.1-98210-1535537618-1631.48110-5-0@isc.org>
 <874lfdgwf6.fsf@pzhukov-workstation.usersys.redhat.com>
 <rt-4.4.1-11120-1535547620-739.48110-0-0@isc.org>
RT-Send-CC:
Content-Length: 1038

Hi Pavel:

Yes, upon closer inspection I did notice that after my initial reply to you.  I can only surmise that 3G lease files are not all that common or we would have had complaints of this more frequently.

Regards,

Thaoms


On Wed Aug 29 13:00:20 2018, pzhukov@redhat.com wrote:
> Hello Thomas,
> 
> Just for clarification.
> I know that tracing is not very popular feature. But the problem is
> users are affected by the problem even if they don't employ tracing but
> dhcp is compiled with enabled tracing (which is by default unless
> --disable-tracing specified) and leases file is greater than 3GB. 
> 
> "Thomas Markwalder via RT" <dhcp-public@isc.org> writes:
> 
> > Hello Pavel:
> >
> > Thanks for submitting the patch for this.  We do not get a lot if
> > issues reported against playback, largely because only our most
> > sophisticated users employ it.  I've marked it for inclusion in 4.4.2.
> > We have not yet decided on a release date for it.
> >
> > Regards,
> >
> > Thomas Markwalder
> > ISC Software Engineering
>