9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] aux/listen changes
Date: Tue, 18 Apr 2017 21:06:26 +0100	[thread overview]
Message-ID: <B1154D99-9A72-4CA5-9F42-E7D37AD5EBDF@quintile.net> (raw)
In-Reply-To: <A2CDB265-E7EA-47F2-8032-7A5ADBD42BC7@stanleylieber.com>


> On 18 Apr 2017, at 16:27, Stanley Lieber <sl@stanleylieber.com> wrote:
> 
> On Apr 18, 2017, at 11:18 AM, Julius Schmidt <aiju@phicode.de> wrote:
>> 
>> can we finally disable bullshit services in /rc/bin/service?
>> basically all services except 17019 and 17020 (i think)
>> 
>> i would also propose (as suggested by someone in #cat-v, sorry forgot whom) that we look for services in /cfg/$sysname/service first.
>> i think this is best done by changing cpurc, i.e. do something like
>> 
>> serviced=/rc/bin/service
>> if(test -d /cfg/$sysname/service)
>>   serviced=/cfg/$sysname/service
>> aux/listen ... -d $serviced ...
>> 
>> this is useful both for server specific configuration but also since /rc/bin/service is under version control.
>> 
>> arguably, we could also use /rc/bin/service.$sysname, but i loathe putting more configuration under /rc/bin.
> 
> All sounds good to me.
> 
> sl
> 

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



  reply	other threads:[~2017-04-18 20:06 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 [this message]
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
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=B1154D99-9A72-4CA5-9F42-E7D37AD5EBDF@quintile.net \
    --to=steve@quintile.net \
    --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).