9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] werc comments egine
Date: Mon, 17 Jan 2022 19:20:34 -0800	[thread overview]
Message-ID: <365B92442B08A87728AA2C4D28F26158@gmail.com> (raw)
In-Reply-To: <4C3A2C43-2475-4B7C-9BF1-B8C01D38680E@stanleylieber.com>

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

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

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

From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] werc comments egine
Date: Tue, 18 Jan 2022 00:23:11 +0000
Message-ID: <4C3A2C43-2475-4B7C-9BF1-B8C01D38680E@stanleylieber.com>

On January 17, 2022 11:47:00 PM UTC, thinktankworkspaces@gmail.com wrote:
>So I deleted everything and started over. Its working now but I still ran into a few problems. 
>
>So you need to log in in order to add a comment. When I log in I still get an error writing data. 
>
>Auth: success
>umask: '/bin/umask' directory entry not found
>mkdir: can't create sites/cirno/_werc/comments: 'sites/cirno/_werc/comments' access permission denied
>ERROR XXX: Could not create comment:  mkdir 57899: error
>cirno/ - Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 - POST - md_handler sites/cirno/index.md - lib/default_master.tpl
>Mon Jan 17 14:54:06 PST 2022 :: cirno :: POST / HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
>tee: cannot open /tmp/fltr_cache/8abfe6173693d0f2edb5404b78cd9aa804db02d6/57917: '/tmp/fltr_cache' does not exist
>mv: can't stat /tmp/fltr_cache/8abfe6173693d0f2edb5404b78cd9aa804db02d6/57917: '/tmp/fltr_cache' does not exist
>Auth: success
>Mon Jan 17 14:54:07 PST 2022 :: cirno :: GET /pub/style/style.css HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
>
>Not really sure why I get this error. The user www should have full access to everything. However I suspect
>an issue with one of the files /bin/umask does not exist in plan9. So I did a grep to search for it
>I found it in two areas. 
>
>/usr/www/werc/apps/bridge/app.rc:88. I would comment it out
>I also belive app.rc:91 is incorrect
>I think app.rc:91 should be
>mkdir -p $dir &&
>
>Auth: success
>sites/cirno/_werc/comments/1642460857/user: ./apps/bridge/app.rc:93: can't open: 'sites/cirno/_werc/comments' does not exist
>Mon Jan 17 15:07:37 PST 2022 :: cirno :: POST / HTTP/1.1 :: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.2 Safari/605.1.15 :: 200 :: http://cirno/
>
>I still got another error. I guess you need to create the directory 'comments' in sites/cirno/_werc/
>
>so I had to manually run
>mkdir -p comments while in sites/cirno/_werc/ directory and then run
>chmod 777 comments
>
>Not exactly happy about that but it works. 
>
>Wiki is also another issue and required the following
>
>mkdir -p sites/cirno/index.md_werc
>chmod 777 index.md_werc
>chmod 777 index.md
>
>I also had to remove umask from apps/dirdir/app.rc
>
>So two directories are 777 and one file. But now my other plan9 users can make changes not that I have
>any users but this is kind of bad. 

sorry i haven't had time to look into this more closely yet, but i run all the werc apps on 9front under rc-httpd, and they all work without modification. most of the errors generated by missing unix commands can be safely ignored *if things are working*. werc was written on linux, and mostly assumes you are running some flavor of plan9port tools on a unix. i will have to look into apps/ further to see if some of these errors can be trimmed.

your errors about the missing directories indicate whatever user is executing werc (whomever rc-httpd is running as) does not have permission to create those missing directories, so is failing. how are you launching rc-httpd, exactly?

the path werc/sites/cirno also seems questionable. the directories under sites/ are meant to correspond to domain names.

sl

  parent reply	other threads:[~2022-01-18 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17  2:56 thinktankworkspaces
2022-01-17  7:43 ` Kurt H Maier
2022-01-17 23:47   ` thinktankworkspaces
2022-01-18  0:23     ` Stanley Lieber
2022-01-18  2:21       ` thinktankworkspaces
2022-01-18  3:20       ` thinktankworkspaces [this message]
2022-01-18  5:06         ` Stanley Lieber
2022-01-18  8:13           ` thinktankworkspaces
2022-01-18  3:20       ` thinktankworkspaces
2022-01-18  7:27       ` thinktankworkspaces
2022-01-17  9:07 thinktankworkspaces

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=365B92442B08A87728AA2C4D28F26158@gmail.com \
    --to=thinktankworkspaces@gmail.com \
    --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).