9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gorka Guardiola Múzquiz" <paurea@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] mkstemp()
Date: Fri, 28 Jan 2005 17:08:03 +0100	[thread overview]
Message-ID: <002d01c50553$8d6de0a0$0200000a@urjc1> (raw)
In-Reply-To: <Pine.LNX.4.58.0501280838100.25505@enigma.lanl.gov>

What about two instances of the same program?. What I meant in my other mail 
is that a big random number would probably suffice, as the probability of 
collision is really low
(as you say we already have user separation).
Even more if it has an identifier per applications (ex. /tmp/acme.23423) 
which also makes the name readable. In any case, if the create fails, you 
can always generate the
random number again.

----- Original Message ----- 
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Sent: Friday, January 28, 2005 4:38 PM
Subject: Re: [9fans] mkstemp()


>
>
> On Fri, 28 Jan 2005 cej@gli.cas.cz wrote:
>
>> need mkstemp() [BSD unistd.h]
>
> why? Your tmp is not my tmp. I see no need for the actual function, just
> make something with the same name that doesn't worry about 'unique' file
> names.
>
> ron
> 



  reply	other threads:[~2005-01-28 16:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 13:39 cej
2005-01-28 13:44 ` Gorka Guardiola Múzquiz
2005-01-29  3:02   ` Scott Schwartz
2005-01-29  3:07     ` boyd, rounin
2005-01-29  3:15       ` Russ Cox
2005-01-29  7:23         ` arisawa
2005-01-29  9:11           ` Russ Cox
2005-01-29 10:11             ` arisawa
2005-01-29 15:11               ` Russ Cox
2005-01-29  8:30       ` geoff
2005-01-28 15:05 ` Russ Cox
2005-01-28 15:38 ` Ronald G. Minnich
2005-01-28 16:08   ` Gorka Guardiola Múzquiz [this message]
2005-01-28 16:16     ` Russ Cox
2005-01-31  8:29 cej

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='002d01c50553$8d6de0a0$0200000a@urjc1' \
    --to=paurea@lsub.org \
    --cc=9fans@cse.psu.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).