Re: Re: Re: [9front] Enabling a service

[Rocky Hotas <rockyhotas@firemail.cc>]

On mag 06 19:00, ori@eigenstate.org wrote:
> % g listen /bin/cpurc
> /bin/cpurc:26: # usb listener
> /bin/cpurc:108: 	aux/listen -q -t /rc/bin/service.auth -d $serviced tcp
> /bin/cpurc:112: 	aux/listen -q -d $serviced tcp
> /bin/cpurc:122: # other /proc files, such as note, so let listen be killed
> 
> the invocation on line 112 is what you're looking for.

Ok! I make a recap if it can be useful for any other having the same
issue.

As in this example

aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp

from

 <https://9p.io/wiki/plan9/Configuring_a_Standalone_CPU_Server/index.html>

`$serviced' is (in my default 9front installation) /rc/bin/service.

After some attempts, this worked for me:

term% cd /rc/bin/service
term% mv !tcp7 tcp7
term% aux/listen -q -d /rc/bin/service tcp

This way, all the services represented by files whose names are in
the form `tcp<port_number>' in /rc/bin/service are enabled.
Files whose names have a trailing `!' are excluded, instead.

The contents of file tcp7 determines how the service will behave when
someone connects to it: in this case,

term% cat tcp7
#!/bin/rc
/bin/cat

And the client will get an echo of anything is typed, due to `cat'.

According to listen(8), the service directory (`/rc/bin/service' in my
example) is also periodically scanned for changes in the files. It gets
updated within seconds probably: so, after running `aux/listen -q
-d /rc/bin/service tcp', if the contents of the file `tcp<port_number>'
or the filename itself are modified, the system will behave accordingly
without need for any other action.

Thank you so much!

Rocky