9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rc: token buffer too short
Date: Wed, 12 Dec 2007 10:14:41 +0000	[thread overview]
Message-ID: <475F38E7.B32653B1@null.net> (raw)
In-Reply-To: <74D6B736-B261-44EC-B2AF-86ACC35E971A@mac.com>

Pietro Gagliardi wrote:
> What I could do instead is
>         u=/tmp/$0$pid$apid$0
>         ...
> but I'd rather not go that way to avoid possible collisions.

Seems that there could be a filesystem that hands out unique names.

Another similar approach would be for the open of a new special
file to create a unique temp file, which would vanish upon final
close, and have the app share/clone the file descriptor, which
could be dup2()ed (or whatever Plan9 equivalent is) to stdout,
stdin, etc., for the various processes in your script.


  reply	other threads:[~2007-12-12 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 17:43 Pietro Gagliardi
2007-12-01 19:09 ` Martin Neubauer
2007-12-11 13:32   ` roger peppe
2007-12-11 19:46     ` Pietro Gagliardi
2007-12-12 10:14       ` Douglas A. Gwyn [this message]
2007-12-12 11:04       ` roger peppe

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=475F38E7.B32653B1@null.net \
    --to=dagwyn@null.net \
    --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).