Re: [9front] werc comments egine

[thinktankworkspaces@gmail.com]

[-- Attachment #1: Type: text/plain, Size: 404 bytes --]

Wow! sl...I just learned a ton in this response from you. Its working default now. I removed my
777 directories and files to make sure it creates comments folder and comments automatic. 
Wiki is working also. Thanks a bunch. It seems i'm not really making the best use of this 
OS or I'm making too many false assumptions.

And the werc is really impresive even if I barely know how to use it. 

Regards

[-- Attachment #2: Type: message/rfc822, Size: 5203 bytes --]

From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] werc comments egine
Date: Tue, 18 Jan 2022 05:06:41 +0000
Message-ID: <51605C26-36E6-4AB4-AF20-6761E2C389F3@stanleylieber.com>

On January 18, 2022 3:20:34 AM UTC, thinktankworkspaces@gmail.com wrote:
>Okay thinking about this. I guess /rc/bin/cpurc has a line
>
>	# cpu+auth server
>	auth/keyfs -wp -m /mnt/keys /adm/keys
>	aux/listen -q -t /rc/bin/service.auth -d $serviced tcp
>
>Which I guess points to tcp services or /rc/bin/services
>
>cpu% cat tcp80
>#!/bin/rc
>exec /rc/bin/rc-httpd/rc-httpd >>[2]/sys/log/www
>cpu% 
>
>So how do I get the user to run this. Do I just pull it out of cpurc and add it to /usr/www/lib/profile or
>clearly i'm confused?
>
>I guess I always drawterm and log in as glenda the run rcpu -u www. So I should do that
>and manually run 
>
>aux/listen -q -t /rc/bin/service.auth -d $serviced tcp

when you boot the system, $user is the hostowner, which refers to the owner of the kernel process. the hostowner ends up owning the disk file server process, as well, but the disk file server programs don't provide any automatic mechanism for violating disk file permissions without writing code or abusing the system's running processes with a special tool such as acid(1).

disk file permissions are completely separate from kernel process permissions, and are controlled by the disk file server process (cwfs or hjfs). by convention, plan 9 arranges for the kernel, auth, and disk file server to honor matching usernames, even though technically they're separate entities.

it looks like your system is running rc-httpd via a tcp80 script launched by the default listen(8) process, which ends up being owned by the special user none, rather than your chosen user www.

here's what i do for 9front.org:

first, move the /rc/bin/services/tcp80 script into /cfg/$sysname/service.www/

then add the following to /cfg/$sysname/cpustart:

auth/as www aux/listen -p 128 -t /cfg/$sysname/service.www

when you reboot, this will start a listener running as user www on the directory /cfg/$sysname/service.www/, and any listener script you put in there will in turn be run as user www.

sl