ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: ecashin@coe.uga.edu (Ed L. Cashin)
Subject: temp file name conflicts in unattended document generation
Date: 01 Nov 1999 14:16:17 -0500	[thread overview]
Message-ID: <m3wvs210qm.fsf@kali.coe.uga.edu> (raw)

Hi.  Most of the time, the files that are generated by TeX and its
friends during processing are named after the source file.  For
example, "foo.tex", when compiled, results in new files like foo.log,
foo.aux, foo.tui, etc., depending on the software in use.

I take advantage of that feature when making documents on behalf of
"client" processes, usually web servers.  Usually I'll add a process
number or a unique identifier for each potential client to the
filename, e.g., "foo-1234.tex".  

That way, the client's files don't step on the toes of other clients
who are trying to generate documents independently and maybe at the
same time.

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?

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/


             reply	other threads:[~1999-11-01 19:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-01 19:16 Ed L. Cashin [this message]
1999-11-01 22:30 ` Hans Hagen
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=m3wvs210qm.fsf@kali.coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    /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).