On Mon, Nov 27, 2000 at 02:39:43AM +0100, Michael Moerz wrote:
> The problem is that metamail makes use of mkstemp and it leaves
> tmp files behind, when it is invoked with a multipart mime
> message. So you can see them in /tmp named mm.XXXXXX .
> My problem now is that it is hardly to track where that tmp-files
> are really created and I can hardly jugde how to fix that properly
> when I discover where the problem originates from.
> So I have two choices:
> 1) I could add each tmp file to a list and clean it up before the
> program leaves. (that would not require to touch even a single
> line of code, but I would have to add some lines that do that)
> 2) I could change the mkstemp code to use tmpfile(), but then I
> would have to change much more of the original code and it
> would be much more likely to introduce new bugs.
>
> Personally I would like to do 1, but 2 seams to be much *cleaner*.
Go for a clean method. If upstream no longer exists, then there won't
even be problems with upstream changing things and having to integrate
patches ;-)
You could use strace to find out what happens to these tmp files.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
