From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] aux/listen changes
Date: Tue, 18 Apr 2017 16:19:29 -0400 [thread overview]
Message-ID: <99147B08-6D16-450F-9F4E-6B34D0019737@stanleylieber.com> (raw)
In-Reply-To: <B1154D99-9A72-4CA5-9F42-E7D37AD5EBDF@quintile.net>
> On Apr 18, 2017, at 4:06 PM, Steve Simon <steve@quintile.net> wrote:
>
> Too you really run different services on different servers?
> All my cpu servers run the same services, whilst the terminals don’t even run listen.
>
> Plan9 has plenty of problems but /rc/bin/service is not a significant one IMHO.
>
> -Steve
Yes, I run different services on several machines that share a disk file system.
Plan 9's best point of separation for integrity of processes is individual kernels. Sometimes you want to isolate stuff that might go nuts or is otherwise unreliable.
Example: crashing my web server (likely) does not cause my e-mail to stop processing.
The point about tracking in the repository is also salient. It makes sense to fall back on sane defaults but also check for site customized alternatives. That's why /cfg exists in the first place. It's a good idea to track (only) the sane defaults in the repository.
sl
next prev parent reply other threads:[~2017-04-18 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 15:18 Julius Schmidt
2017-04-18 15:27 ` [9front] " Stanley Lieber
2017-04-18 20:06 ` Steve Simon
2017-04-18 20:12 ` Kurt H Maier
2017-04-18 20:23 ` Stanley Lieber
2017-04-18 22:39 ` Steve Simon
2017-04-18 22:55 ` Stanley Lieber
2017-04-18 20:19 ` Stanley Lieber [this message]
2017-04-19 8:05 cinap_lenrek
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=99147B08-6D16-450F-9F4E-6B34D0019737@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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).