What follows is the beginning and end of a thread in c.o.o.misc about a problem that was becoming acute, as explained below. I am posting here because others may see the same problem and may be helped by the solution that was found.
On Fri, 30 Nov 2001 09:35:02, [EMAIL PROTECTED] (Hartmut Krafft) opined: > On Fri, 30 Nov 2001 02:35:06, [EMAIL PROTECTED] (Stan > Goodman) wrote: > When I first installed MCP many moons ago, the boot partition had > plenty of free space. The partition then contained only the operating > system plus Java11. Now it has Java13 too, but when that was added > there was still about 50MB free space. > > Lately I have noticed that every time I look at the OD Control-Center > free-space monitor for the partition, there is less there. Yesterday I > noticed that (again -- this is not the first time) the monitor showed > 2.2MB, so I deleted the the Java11 demos directory, which got it up to > about 5MB. Now it is 4.1MB again. I would delete Java11 altogether, > but I understand Netscape 4.61 requires it, and I don't want to lose > it. > > Yesterday I searched for *.log and *.ini files, to see if there were > large files of this sort, and deleted some of the larger ones, but > there were none that were really enormous. Where the deuce is the boot > partition evaporating to? What can I do to avoid filling up the > partition completely, which is what looks to happen pretty soon? I started tracking directory sizes yesterday in the evening, when free-space had got down to 3.1MB (this morning I was down to 2.5MB). I used Filestar/2, which makes this tracking very easy. I had also noticed that decreases in free space were correlated with usage of various versions of Mozilla. Browsers are not in the boot partition, but in a partition containing applications. At this critical moment, I got a suggestion from Britt Turnbull to check out any TMP directories on the boot partition. Voila! C:\TCPIP\TMP had some 56 files, dated from the end of October until today (1 December), which is indeed the period during which I have been using IBM Web Browser and Warpzilla. These files contain mostly gibberish, but also hints that they are related to brower caching -- and sure enough, they have names like "jar_cache28962.tmp". The total size of these files is nearly 20MB, which is about the size of the missing disk space. Lots of "coincidences" here. To me, in my naivete, "TMP" in this context means that files so named will be deleted without my intervention when the reason for writing them has passed. That they are not can only be called a pernicious bug. "Sabotage" also comes to mind. If there is a reason for not doing this, it would have been a kindness for the developers to give a hint of the fact to users, so they could take their own measures, and not have to spend hours and more in hunting for where their disk space is going. The fact that the program is a Beta version has little to do with tying up a simple loose end like this. But now that I know that I have to perform this function myself, since the developers have failed to make automatic provision for it, the directory (now moved to a different partition) will be emptied out automatically at each boot. -- Stan Goodman Qiryat Tiv'on Israel To send me email, please note that email addressed to "SPAM-FOILER" will not reach me, and will not be read. Please replace "SPAM-FOILER" with "stan". -- Stan Goodman Qiryat Tiv'on Israel To send me email, please note that email addressed to "SPAM-FOILER" will not reach me, and will not be read. Please replace "SPAM-FOILER" with "stan".
