Comment 2 for bug 1658027

Hi
Thanks for you prompt response. Given the age of the version I am running, I have low expectations around corrective action. I did read up bug reports where this issue was fixed prior to the release I have.

On a slightly wider issue, I have attempted to conduct troubleshooting on this problem. My "findings" include:

 - no known Linux application that will identify what process/program has created any given file.

 - I don't know of any marker that apt and related utilities might include in a file to identify the source utility.

 - I have looked at the /etc/apt/apt.conf/10Periodic file and turned on verbose "3" mode. No email was created when the cache file was created a 6:25am.

 - The MaxSize is set to "500" which is well under the capacity of the HD. Whichever program creates the cache files is ignoring the directory size limit.

 - The problem appears to have developed spontaneously without user intervention.

 - If there is a problem with a broken file, I don't know how to find it or fix it. Running "clean" gets rid of the cache files but doesn't stop them being created.

In short, troubleshooting apt problems seems to be more difficult that it should be. Perhaps this may be an area worth working on in future releases.

In the mean time, I will just set up a daily cron "clean" job to clear the cache. I don't expect any action or further discussion.

Cheers

Dazz