From: "Scott Flowers" <flowerss@cranky.ca>
To: 9front@9front.org
Subject: Re: [9front] Enabling a service
Date: Mon, 06 May 2024 09:16:01 -0600 [thread overview]
Message-ID: <75fdf3c0-e0f6-4342-9b1c-9c65fc790852@app.fastmail.com> (raw)
In-Reply-To: <7D3BF4392AC2C46E8146B2A18FA14471@eigenstate.org>
--- fqa7.ms
+++ fqa7.ms
@@ -1356,11 +1356,18 @@
causes the shell script
.CW /rc/bin/cpurc
to be run at boot time, which in turn launches a listener that scans the
+.CW /cfg/$sysname/service
+directory for scripts corresponding to various network ports. If that directory doesn't exist,
+.CW /cfg/default/service
+and
.CW /rc/bin/service
-directory for scripts corresponding to various network ports. Read:
+are checked in order. The files in
+.CW /rc/bin/service
+are primarily intended to serve as examples. Read:
.ihtml a <a href="http://man.9front.org/8/listen">
.CW listen(8) .
.ihtml a
+
The scripts
.CW tcp17019
and
Scott Flowers
flowerss@cranky.ca
On Mon, 6 May 2024, at 06:43, ori@eigenstate.org wrote:
> Quoth Rocky Hotas <rockyhotas@firemail.cc>:
> >
> > How to enable such a service? I guess that my system is not a CPU server,
> > probably it's just a file server. Does this matter?
>
> yes, listen(1) is only started on cpu servers by default.
> you can run it manually if you want.
>
>
next prev parent reply other threads:[~2024-05-06 15:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 11:32 Rocky Hotas
2024-05-06 11:58 ` Alex Musolino
2024-05-06 12:43 ` ori
2024-05-06 15:16 ` Scott Flowers [this message]
2024-05-06 15:37 ` sirjofri
2024-05-06 16:32 ` Stanley Lieber
2024-05-06 22:18 ` Rocky Hotas
2024-05-06 22:59 ` ori
2024-05-06 23:00 ` ori
2024-05-07 8:22 ` Rocky Hotas
2024-05-07 8:29 ` Frank D. Engel, Jr.
2024-05-07 9:03 ` Rocky Hotas
2024-05-07 9:14 ` sirjofri
2024-05-07 21:11 ` Shawn Rutledge
2024-05-07 21:35 ` Kurt H Maier
2024-05-07 21:45 ` sirjofri
2024-05-07 21:54 ` sl
2024-05-07 21:58 ` sl
2024-05-07 23:15 ` Lennart Jablonka
2024-05-07 23:16 ` Shawn Rutledge
2024-05-07 23:45 ` Shawn Rutledge
2024-05-08 0:34 ` Kurt H Maier
2024-05-08 0:35 ` sl
2024-05-08 1:05 ` Jacob Moody
2024-05-08 1:24 ` sl
2024-05-08 7:22 ` hiro
2024-05-08 14:04 ` Stanley Lieber
2024-05-08 12:08 ` Stuart Morrow
2024-05-08 16:37 ` Brian Stuart
2024-05-08 20:16 ` hiro
2024-05-08 21:26 ` Stuart Morrow
2024-05-08 21:17 ` Disconnection-tolerant / distributed filesystems (was Re: [9front] Enabling a service) Shawn Rutledge
2024-05-08 14:25 ` [9front] Enabling a service Jacob Moody
2024-05-08 3:41 ` Ori Bernstein
2024-05-08 4:09 ` sl
2024-05-08 8:39 ` Frank D. Engel, Jr.
2024-05-08 14:17 ` Jacob Moody
2024-05-08 15:49 ` Frank D. Engel, Jr.
2024-05-08 16:10 ` Jacob Moody
2024-05-08 16:33 ` Frank D. Engel, Jr.
2024-05-08 17:27 ` Jacob Moody
2024-05-08 18:00 ` Steve Simon
2024-05-08 19:46 ` hiro
2024-05-08 19:46 ` Roberto E. Vargas Caballero
2024-05-08 20:34 ` tlaronde
2024-05-08 14:57 ` Lucas Francesco
2024-05-08 15:10 ` an2qzavok
2024-05-08 2:11 ` Thaddeus Woskowiak
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=75fdf3c0-e0f6-4342-9b1c-9c65fc790852@app.fastmail.com \
--to=flowerss@cranky.ca \
--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).