* [9front] /rc/bin/cpurc default listen -q
@ 2021-01-01 17:10 Stanley Lieber
2021-01-01 17:43 ` ori
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Stanley Lieber @ 2021-01-01 17:10 UTC (permalink / raw)
To: 9front
proposal:
these flags should somehow be more easily customizable without stepping on the tracked file.
sl
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [9front] /rc/bin/cpurc default listen -q
2021-01-01 17:10 [9front] /rc/bin/cpurc default listen -q Stanley Lieber
@ 2021-01-01 17:43 ` ori
2021-01-01 17:43 ` hiro
2021-01-02 0:18 ` Alex Musolino
2 siblings, 0 replies; 5+ messages in thread
From: ori @ 2021-01-01 17:43 UTC (permalink / raw)
To: 9front
Quoth Stanley Lieber <sl@stanleylieber.com>:
> proposal:
>
> these flags should somehow be more easily customizable without stepping on the tracked file.
>
> sl
>
Are cpurc and termrc candidates for /sys/lib/dist?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] /rc/bin/cpurc default listen -q
2021-01-01 17:10 [9front] /rc/bin/cpurc default listen -q Stanley Lieber
2021-01-01 17:43 ` ori
@ 2021-01-01 17:43 ` hiro
2021-01-02 0:18 ` Alex Musolino
2 siblings, 0 replies; 5+ messages in thread
From: hiro @ 2021-01-01 17:43 UTC (permalink / raw)
To: 9front
how far is the BurnzezD init system replacement? :)
On 1/1/21, Stanley Lieber <sl@stanleylieber.com> wrote:
> proposal:
>
> these flags should somehow be more easily customizable without stepping on
> the tracked file.
>
> sl
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] /rc/bin/cpurc default listen -q
2021-01-01 17:10 [9front] /rc/bin/cpurc default listen -q 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
2 siblings, 1 reply; 5+ messages in thread
From: Alex Musolino @ 2021-01-02 0:18 UTC (permalink / raw)
To: 9front
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] /rc/bin/cpurc default listen -q
2021-01-02 0:18 ` Alex Musolino
@ 2021-01-02 0:28 ` Stanley Lieber
0 siblings, 0 replies; 5+ messages in thread
From: Stanley Lieber @ 2021-01-02 0:28 UTC (permalink / raw)
To: 9front
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-01-02 0:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-01 17:10 [9front] /rc/bin/cpurc default listen -q 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 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).