On 10/10/07, Marco d'Itri [EMAIL PROTECTED] wrote:
On Oct 09, Lars Lindner [EMAIL PROTECTED] wrote:
That seems reasonable. Do you think it worthwhile to close and reopen
the database forcibly every so often, to prevent this?
Yes, I think it would. But it still would be a workaround.
On Oct 09, Lars Lindner [EMAIL PROTECTED] wrote:
That seems reasonable. Do you think it worthwhile to close and reopen
the database forcibly every so often, to prevent this?
Yes, I think it would. But it still would be a workaround.
I'd rather have a simple workaround than the current state
On 10/9/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
On Sun, Oct 07, 2007 at 07:34:59PM +0200, Lars Lindner wrote:
Known problem. No solution in sight. I already tried reproducing the
effect with a test program using the same schema and similar
SQL statements as Liferea, but it doesn't
On Sun, Oct 07, 2007 at 07:34:59PM +0200, Lars Lindner wrote:
Known problem. No solution in sight. I already tried reproducing the
effect with a test program using the same schema and similar
SQL statements as Liferea, but it doesn't show the same problem.
I have the feeling this might be
Package: liferea
Version: 1.4.3-1
Severity: normal
I never quit liferea. It runs until either it crashes or my entire
system crashes. This used to be fine, but today I've discovered that
it isn't caching updated feeds to disk. So after a crash I restart it
and it has three hundred new articles
On 10/7/07, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
Package: liferea
Version: 1.4.3-1
Severity: normal
I never quit liferea. It runs until either it crashes or my entire
system crashes. This used to be fine, but today I've discovered that
it isn't caching updated feeds to disk. So
6 matches
Mail list logo
