From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 15 Dec 2013 11:00:52 -0500
To: 9fans@9fans.net
Message-ID: <e5bd44a79dcfe0cf23324042620efad6@mikro>
In-Reply-To: <CABwHSOuN_aMktkkt9kN5xqHGYBBwfX0WZ8Q6V3n8_NhY-Nus0g@mail.gmail.com>
References: <CABwHSOvtsX2e2JcozZu=iYaPjO2OYcKO5Sfg45TutSTVOcx5CQ@mail.gmail.com>
	<20131213173148.GA85777@shells>
	<CABwHSOuN_aMktkkt9kN5xqHGYBBwfX0WZ8Q6V3n8_NhY-Nus0g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Can't start multiple copies of acme
Topicbox-Message-UUID: 9b00a704-ead8-11e9-9d60-3106f5b1d025

On Sun Dec 15 10:23:13 EST 2013, blake@mcbride.name wrote:

> I checked.  The following shell script does the trick:
>
>
> #
> mkdir /tmp/acme-$$
> NAMESPACE=/tmp/acme-$$ acme "$@"

this is swimming up stream.  acme's model is to run 1 copy of acme,
and edit all files in it.  many things, such as plumbing, will work
better with 1 copy of acme.

by the way, this limitation is p9p specific.  but still it's no
fun to have the same file get plumbed to every acme.

- erik