9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How to run different services on multiple cpu servers
Date: Mon, 15 Mar 2004 10:01:00 +0100	[thread overview]
Message-ID: <be0c239ed4ef4fde0f7fcbf0135f6e1a@plan9.escet.urjc.es> (raw)
In-Reply-To: <20040313005247.GD7139@cassie.foobarbaz.net>

[-- Attachment #1: Type: text/plain, Size: 84 bytes --]

I have a switch in cpurc that starts different services for
different cpuservers.

[-- Attachment #2: Type: message/rfc822, Size: 2613 bytes --]

From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How to run different services on multiple cpu servers
Date: Fri, 12 Mar 2004 16:52:47 -0800
Message-ID: <20040313005247.GD7139@cassie.foobarbaz.net>

On Fri, Mar 12, 2004 at 11:54:43AM -0500, Brantley Coile wrote:
> I've been running a single cpu server for 9 years.
> I'm now setting up several.  What's customary for
> configing the serivces?  I created a new directory name service.<sysname>
> and moved things around in there.  How do you folks do it?

That's exactly what I did. It works quite well for me.
I'd be curious to hear other people's solutions, though.

-- 
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin

      parent reply	other threads:[~2004-03-15  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 16:54 Brantley Coile
2004-03-13  0:52 ` Christopher Nielsen
2004-03-14  6:42   ` lucio
2004-03-14 16:30     ` ron minnich
2004-03-14 22:36       ` Christopher Nielsen
2004-03-14 23:54         ` Charles Forsyth
2004-03-15  0:05           ` Geoff Collyer
2004-03-15  9:01   ` Fco.J.Ballesteros [this message]

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=be0c239ed4ef4fde0f7fcbf0135f6e1a@plan9.escet.urjc.es \
    --to=nemo@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).