ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: ecashin@coe.uga.edu (Ed L. Cashin)
Cc: "Context List" <ntg-context@ntg.nl>
Subject: Re: temp file name conflicts in unattended document generation
Date: 03 Nov 1999 14:50:31 -0500	[thread overview]
Message-ID: <m3d7truzg8.fsf@kali.coe.uga.edu> (raw)
In-Reply-To: <000b01bf2531$541bda80$0c01a8c1@loginbv.com>

Gilbert van den Dobbelsteen <gilbert@panter.soci.aau.dk> writes:

> For Hans: $$ returns the curent process Id in unix, which is
> guaranteed to be unique.

Disclaimer: although somewhat relevant to a discussion of unique
	    identifiers for document-generation runs, this is a bit
	    off topic.

Unique by process, yes, but an interesting development in perl is
mod-perl, where the compiled perl resides inside the web server
process until the web server dies.

That means that different invocations of the same perl code with the
same process id (viz., the web server's) could be producing different
documents.  So often I avoid the $$ technique for CGI and use a random
letter/number plus lockfiles instead.

I like Taco's suggestion of using a directory name that contains the
identifier for a given run. 

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


  parent reply	other threads:[~1999-11-03 19:50 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
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 [this message]
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=m3d7truzg8.fsf@kali.coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    --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).