From: Edouard Klein <edou@rdklein.fr>
To: 9fans@9fans.net
Subject: Re: [9fans] Content of your /rc/bin/service or /dis/svc ?
Date: Tue, 05 Mar 2024 22:28:01 +0100 [thread overview]
Message-ID: <878r2w1hsa.fsf@rdklein.fr> (raw)
In-Reply-To: <e4ba4750-049f-4ac2-bb20-c41d9a9938e8@sirjofri.de>
Hi,
Thank you for your answer.
sirjofri <sirjofri+ml-9fans@sirjofri.de> writes:
> Hello,
>
> I don't use /rc/bin/service anymore, but I use /cfg/machinename/service instead. My contents are copies of what's in /rc/bin/service or my own scripts:
I assume that you then bind-mount /cfg/machinename/service to that
machine's /rc/bin/service ?
>
> tcp80 - web server
> tcp443 - web server but wrapped in tls
> ...
>
> I have some cifd running, some irc server that translates to grid chat, my mail
> server (smtp and imap4), and fingerd, the files follow the usual scheme tcpXXX.
> I probably missed one service or the other, but aux/listen is simple enough to
> set up custom servers with arbitrary functionality.
>
Would you mind sharing your fingerd and irc server ? For finger my plan
is to turn this one:
https://github.com/michael-lazar/finger2020/blob/master/finger2020 into
a multi-user version, but if there already is one I won't bother.
> If you have exact questions about aux/listen functionality or you don't understand something, just ask :)
>
- I noticed some tcpXXX files use exec for their last line, and some
don't. Is there a reason ? My understanding is that exec saves one call
to fork per connection, and thus it would be best if it was always used.
- I noticed Inferno makes great use of servers that speak 9P on their
stdstream, with its
mount {some-program} /mnt/toto
These programs are trivial to expose thanks to listen:
listen -v 'tcp!*!toto' {some-program&}
On Plan9, I ran into rc's cmd <[0=1] | echo 0 > /srv/name, then mount
/srv/name /n/toto.
- Is there a inferno-like shorthand for Plan 9 ?
- Why the "echo 0" ? (I'm not familiar with rc).
> Btw it's quite common to "deactivate" services by renaming the files to have a
> leading "!". In general, everything that follows the naming scheme
> <protocol><port> and is executable will work.
>
why not just chmod -x them ? In a multiuser system, users may not have
the right to rename them.
Thank you for your help :)
Cheers,
Edouard.
>
> sirjofri
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf73851503467346f-Maa2def04fcfcb1e92523c45d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2024-03-05 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 10:34 Edouard Klein
2024-03-02 11:54 ` sirjofri
2024-03-05 21:28 ` Edouard Klein [this message]
2024-03-05 21:59 ` sirjofri
2024-03-05 22:47 ` a
2024-03-06 0:53 ` hiro
2024-03-06 11:03 ` Edouard Klein
2024-03-06 10:42 ` Edouard Klein
2024-03-06 11:06 ` Edouard Klein
2024-03-06 10:28 ` Edouard Klein
2024-03-06 12:52 ` sirjofri
2024-03-06 15:12 ` Edouard Klein
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=878r2w1hsa.fsf@rdklein.fr \
--to=edou@rdklein.fr \
--cc=9fans@9fans.net \
/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).