From: sqweek <sqweek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 2 acmes using plan9port
Date: Fri, 20 Feb 2009 13:56:55 +0900 [thread overview]
Message-ID: <140e7ec30902192056t190e7fe6kb9bd177aa90b81@mail.gmail.com> (raw)
In-Reply-To: <df49a7370902190523l239e80k615e7024e6afa1c3@mail.gmail.com>
On Thu, Feb 19, 2009 at 10:23 PM, roger peppe <rogpeppe@gmail.com> wrote:
> On 19/02/2009, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
>> what needs to be done in order to be able to run two acme programs?
>> When I try to run it twice I get
>>
>> 9pserve: announce unix!/tmp/ns.ruda.:0/acme: Address already in use
>> acme: can't post service: 9pserve failed
>
> i'd just change $NAMESPACE, as documented in intro(4).
Heh, I'm doing both of the suggestions in this thread, with a wrapper script:
http://sqweek.dnsdojo.org/plan9/acme
-sqweek
next prev parent reply other threads:[~2009-02-20 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 11:25 Rudolf Sykora
2009-02-19 12:46 ` erik quanstrom
2009-02-19 13:23 ` roger peppe
2009-02-20 4:56 ` sqweek [this message]
2009-02-20 8:34 ` Rudolf Sykora
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=140e7ec30902192056t190e7fe6kb9bd177aa90b81@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@9fans.net \
/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).