From: Hans Hagen <pragma@wxs.nl>
Cc: NTG-ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: temp file name conflicts in unattended document generation
Date: Mon, 01 Nov 1999 23:30:46 +0100 [thread overview]
Message-ID: <381E1496.5A90@wxs.nl> (raw)
In-Reply-To: <m3wvs210qm.fsf@kali.coe.uga.edu>
Ed L. Cashin wrote:
> I notice that occasionally I see a context-generated filename that is
> not related to the source filename, e.g., "texutil.tuo" and
> "cont-opt.bak". It seems like these files may cause collisions when
> two instances of context are running in the same directory on separate
> sources, e.g. if, in /var/tmp, foo-2222.tex and foo-3333.tex are being
> compiled simultaneously by context.
>
> Is that a valid concern? If so, is there a way to specify an "id"
> string for use in the tempfile names?
I share your problem -) Which is why currently the opt file is already
taken care of. One reason for using a standard name, is that is eases
removing old files, (since I often run on overloaded systems this makes
sense). I think it indeed makes sense to treat the texutil.tuo file in
the same way, so I'll look into it. I have to updat emy perl 'purge'
script anyway -)
BTW, some file duplicated are hard to catch, like buffers with the ame
name and differrent content. But I can make that something optional,
Remind me to solve this (I'm currently updating / reinstalling /
cleaning up my main system to a larger disk, so I don't play with the
sources currently).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-11-01 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-01 19:16 Ed L. Cashin
1999-11-01 22:30 ` Hans Hagen [this message]
1999-11-02 11:04 ` Wybo Dekker
1999-11-02 12:53 ` Gilbert van den Dobbelsteen
1999-11-02 15:45 ` Taco Hoekwater
1999-11-03 19:50 ` Ed L. Cashin
1999-11-04 9:15 ` Gilbert van den Dobbelsteen
1999-11-02 10:03 ` Taco Hoekwater
1999-11-03 19:50 ` Ed L. Cashin
1999-11-04 7:59 ` Hans Hagen
1999-11-04 10:13 ` Taco Hoekwater
1999-11-04 15:09 ` Ed L. Cashin
1999-11-04 16:31 ` Hans Hagen
1999-11-05 14:49 ` Ed L. Cashin
1999-11-05 19:03 ` Hans Hagen
1999-11-05 19:55 ` Hans Hagen
1999-11-08 16:53 ` Ed L. Cashin
1999-11-09 9:27 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=381E1496.5A90@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).