Bug 215167 - kconf_update's update.log should have logrotate mechanism
Summary: kconf_update's update.log should have logrotate mechanism
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-18 20:13 UTC by Ludwin Janvier
Modified: 2024-09-14 16:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ludwin Janvier 2009-11-18 20:13:08 UTC 
Version:            (using KDE 4.3.2)
Installed from:    Ubuntu Packages

In about 1 year, kconf produced a 10Mo file in every user's home (in fact, in $HOME/.kde/share/apps/kconf_update/log/update.log).
Its growing seems to be unstoppable.

It's not a matter of storage cost, but this file is modified everyday, and takes an important part in a daily backup - specially if you have dozen of users.

I know I could just ignore this file, but I think KDE would be greater if one of its components could do this maintenance job for me.
Comment 1 Christoph Cullmann 2024-09-14 16:18:16 UTC 
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann