9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] CPU Server
Date: Thu, 16 Aug 2007 09:29:15 -0400	[thread overview]
Message-ID: <4e8fc2f9c4ec6cb5947ce89b2834f31c@quanstro.net> (raw)
In-Reply-To: <8fae17cd534e3a5bddef97750e5bdcab@plan9.jp>

> Hello,
> 
> I have a question regarding cpurc. I managed to set up a combined cpu/auth
> server by loosely following the wiki instructions.
> 
> If I understand correctly, the lines
> 
> if(! test -e /rc/bin/service.auth/il566){
> 	mv /rc/bin/service.auth/authsrv.il566 /rc/bin/service.auth/il566
> 	mv /rc/bin/service.auth/authsrv.tcp567 /rc/bin/service.auth/tcp567
> 	mv /rc/bin/service/il566 /rc/bin/service/_il566
> 	mv /rc/bin/service/tcp567 /rc/bin/service/_tcp567
> }
> 
> make the auth server listen on the right ports. Is there a likely scenario
> where these will be executed again after the first time the server boots, or
> can I remove them?
> 
> Please let me know if I'm missing something obvious. I'm quite new to Plan 9.
> 
> Cheers
> Rob

you're supposed to do that once.

this is what i have at home

	cpu% lc /rc/bin/service.auth
	!tcp110	il566	tcp22	tcp566	tcp567	tcp995

you may not want ssh.  to keep ssh from starting

	cpu% mv tcp22 !tcp22

of course, i don't have il567 or tcp567 in /rc/bin/service.
just rm them of they're there.

to turn all these  services on, you need to listen for them
from cpurc.  these are the last two lines of mine

	aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service il
	aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp

though if you don't use ken's fileserver, you don't need the
first line as you don't need il.

- erik



  reply	other threads:[~2007-08-16 13:29 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 22:13 Rodolfo (kix)
2007-08-16  1:26 ` geoff
2007-08-16 13:18   ` rob
2007-08-16 13:29     ` erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-28  3:09 Joshua Wood
2007-12-22 23:12 "Rodolfo \"kix\" Garci­a"
2007-12-22 23:15 ` Iruata Souza
2007-12-23  3:13 ` John Soros
2007-12-23  3:35   ` erik quanstrom
2007-12-27 16:16     ` "Rodolfo \"kix\" Garci­a"
2004-02-07  0:24 [9fans] cpu server vdharani
2004-02-06 22:50 ` Jim Choate
2004-02-07  3:41   ` Bruce Ellis
2004-02-07 14:48     ` Jim Choate
2004-02-07 15:21       ` Bruce Ellis
2004-02-07 16:05         ` Jim Choate
2004-02-07 19:54           ` Charles Forsyth
2004-02-07 22:26             ` a
2004-02-07 23:16               ` andrey mirtchovski
2004-02-09 17:47                 ` rog
2004-02-09 18:19                   ` andrey mirtchovski
2004-02-09 18:43                     ` rog
2004-02-09 18:49                       ` andrey mirtchovski
2004-02-09 18:49                     ` rog
2004-02-09 18:50                       ` andrey mirtchovski
2004-02-09 19:32                     ` 9nut
2004-02-09 18:44                       ` andrey mirtchovski
2004-02-10  1:38                     ` Kenji Okamoto
2004-02-10  1:40                       ` David Presotto
2004-02-10  1:50                       ` boyd, rounin
2004-02-10  1:11                         ` andrey mirtchovski
2004-02-10  3:03                           ` Lyndon Nerenberg
2004-02-10  5:00                           ` Geoff Collyer
2004-02-11  3:14                             ` Jack Johnson
2004-02-08  1:04               ` Taj Khattra
2004-02-08  1:20             ` Jim Choate
2004-02-08  2:56               ` Bruce Ellis
2004-02-08  2:40           ` Bruce Ellis
2004-02-07  8:18   ` andrey mirtchovski
2004-02-07 11:12     ` Bruce Ellis
2004-02-07 11:33     ` a
2004-02-07 13:30     ` boyd, rounin
2004-02-07 13:38     ` boyd, rounin
2004-02-07 14:51     ` Jim Choate
1998-07-13 15:46 [9fans] CPU Server Franklin

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=4e8fc2f9c4ec6cb5947ce89b2834f31c@quanstro.net \
    --to=quanstro@quanstro.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).