9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: fs customization (was: Re: [9fans] Terminals)
Date: Wed, 18 Apr 2001 15:45:49 +0200	[thread overview]
Message-ID: <200104181345.PAA01027@copernicus.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 18 Apr 2001 09:36:25 -0400." <200104181336.JAA23868@smtp2.fas.harvard.edu>

Thanks for the general reply!

> To answer your specific questions, you'd probably want
> to start the auth services only in the case for your auth
> server.

To focus in: how does the following instruction for setting up
a standalone auth server translate to the fs situation?
If I remove files from /rc/bin/service, they also disappear for
the non-auth cpu servers.
Is the trick to add an /rc/bin/service.cpu containing the forwarding
services, together with listen lines for that directory?

: Remove /rc/bin/service/il566 and /rc/bin/service/tcp567. They proxy
: calls for the authentication services to the authentication server.
: On the authentication server itself, you'll want to run different
: services on those ports. To run them,
:
: cd /rc/bin/service.auth
: mv authsrv.il566 il566
: mv authsrv.tcp567 tcp567

I'm sorry to keep asking, but I want to make sure I understand.
Axel.



  reply	other threads:[~2001-04-18 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 13:36 Russ Cox
2001-04-18 13:45 ` Axel Belinfante [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-18 13:55 forsyth
2001-04-18 13:54 Russ Cox
2001-04-12 17:40 [9fans] Terminals Dave Iafrate - CSCI/F1997
2001-04-13  2:45 ` Dan Cross
2001-04-18 13:26   ` fs customization (was: Re: [9fans] Terminals) Axel Belinfante

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=200104181345.PAA01027@copernicus.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).