lynx-dev LYNX: "stuff in tmp-space"

[David Combs]

Just got this lynx email (no subject), about
Lynx keeping files in /tmp or somewhere, and
that filling up, and having to be cleaned by hand,
I suppose, if Lynx crashed and didn't get to
finish properly.

If so, then maybe lynx could write into a LOCAL
file (in current pwd) a file containing the NAMES
of any files it wrote into /tmp or wherever.

When lynx exits properly and deletes those files,
then AFTER doing that, it can delete the names-file.

that way, we can edit that names file, and on unix
stick "rm -i" at the left of each line,
and run or "source" the thing, if we want.

Here's the posting I saw:

> From address@hidden Fri Aug  7 19:35:44 1998
> Date: Fri, 7 Aug 1998 21:13:05 -0500
> From: Russell Alderson <address@hidden>
> To: address@hidden
> Sender: address@hidden
> Precedence: bulk
> Reply-To: address@hidden
> 
> Observed in Lynx 2.6 and 2.8 running in Linux: 
> 
> When I downloaded a file to my home directory via "Save to disk," the 
> temp copy of the file lingered in the tempspace for the remainder of the
> Lynx session or until I shelled out and removed it manually.  At the end
> of the session Lynx did remove all remaining tempfiles it generated. 
> 
> I became aware of this only after my ISP put quotas on the default 
> tempspace, /tmp/.  Evidently, long sessions of heavy downloading built 
> up large bunches of tempfiles--probably enough to constitute /tmp/ 
> abuse.  I have already defined LYNX_TEMP_SPACE to point into the home 
> directory to buy some wiggle room. 
> 
> In LYDownload() of LYDownload.c, where Lynx places the file in home, 
> the VMS side first tries to rename() the file out of the tempspace. 
> Can rename() be applied safely on the Unix side as well?  Or removing 
> the tempfile after a successful copy? 
> 
> /\/ QWKRR128 V5.10 [R]
>                                                                             
>