9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] /rc/bin/cpurc default listen -q
Date: Fri, 01 Jan 2021 19:28:21 -0500	[thread overview]
Message-ID: <83DB2098-B3EA-4C8B-9B2B-A658DD5DFAB4@stanleylieber.com> (raw)
In-Reply-To: <255BB1F245E53A8FF74C873ECE1AC7CF@musolino.id.au>

On January 1, 2021 7:18:49 PM EST, Alex Musolino <alex@musolino.id.au> wrote:
>> proposal:
>> 
>> these flags should somehow be more easily customizable without
>> stepping on the tracked file.
>
>I've achieved this with the following in /cfg/$sysname/cpustart:
>
>	auth/as upas aux/listen -p 20 -t /cfg/$sysname/service.mail
>	auth/as www aux/listen -p 100 -t /cfg/$sysname/service.www
>	auth/as alex aux/listen -p 5 -t /cfg/$sysname/service.alex
>
>Perhaps this could work for you too?
>
>--
>Cheers,
>Alex Musolino
>

my point is the defaults for the listener that scans service/ are immutable unless you want to modify a file that's tracked in the mercurial repository.

i think you're right that simply moving more of the default tcp/il/whatever scripts under a separate listener is the cleanest solution. i do run lots of individual instances of listen1, but i didn't considered setting up separate instances of listen (not listen1) to scan separate directories.

my use case here is simply removing the -q flag from listen.

sl

      reply	other threads:[~2021-01-02  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 17:10 Stanley Lieber
2021-01-01 17:43 ` ori
2021-01-01 17:43 ` hiro
2021-01-02  0:18 ` Alex Musolino
2021-01-02  0:28   ` Stanley Lieber [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=83DB2098-B3EA-4C8B-9B2B-A658DD5DFAB4@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).