Essentially a feature to store only enough pcaps to fill the disk up to x%. Once that disk use is reached, pcaps are deleted in the order they were recorded, freeing space for newer pcaps.
OpenFPC uses this feature of Daemonlogger in conjunction with its own capability to roll the session files off the database to accomplish FPC of the most recent time period that there is sufficient storage to handle.
I'm planning to work on this after the InnoDB VIEW issue. If you know of a good / preferred way to implement this, I'll follow your lead.
Essentially a feature to store only enough pcaps to fill the disk up to x%. Once that disk use is reached, pcaps are deleted in the order they were recorded, freeing space for newer pcaps.
OpenFPC uses this feature of Daemonlogger in conjunction with its own capability to roll the session files off the database to accomplish FPC of the most recent time period that there is sufficient storage to handle.
I'm planning to work on this after the InnoDB VIEW issue. If you know of a good / preferred way to implement this, I'll follow your lead.