World: r3wp

It seems that the PID file location recent change was a bad move, 
/var/run is by default only writable by root...To workaround that, 
user should create a sub-folder as root and then chown it to the 
application user to allow it to write PID files there : http://serverfault.com/questions/159334/what-permission-to-write-pid-file-in-var-run

Kaj: so, this means that an install script would be required for 
Cheyenne to be able to run on UNIX, this is not something that I 
want for Cheyenne unless really necessary. Do you see any simple 
solution to that issue? If not, I'll revert it to write in /tmp by 
default and add a config option to let users choose alternative location 
when desired.

I'll have to do some more digging Doc, and maybe see what do* does 
since I haven't tried that. I'll actually read some source if need 
be. ;-) 


What I saw with your new change is something I also saw once with 
the previous approach. Plain CGI worked fine until an RSP was run, 
then the CGI failed, *then* both the test RSP and test RSP web app 
started returning with garbage at the top of the page. More garbage 
each time, like a buffer was being added to. Then the plain CGI worked 
again. Doing a reset on the workers solves the garbage problem.


My Cheyenne EXE is from 2009 so I'll check for a new one before doing 
anything else.

Also, the version I have still says "> Catched Error <" which might 
read better as "> Caught Error <". That may be in recent versions.

From 2009 -> more than 90 revisions since then, these issues have 
been solved a long time ago :-)

Are you using the official binary v0.9.19?

It looks like I really need to make a new official release with new 
binaries.

The EXE doesn't list the Cheyenne version, and I dont think the server-software 
result gives that either, so what's the best way to check?

>> p: open http://domain.com
>> p/locals/headers/server

Cheyenne/0.9.19

So here is my new init.d file:
#! /bin/sh
# /etc/init.d/cheyenne
#

# Some things that run always
#touch /var/lock/blah

STARTSCRIPT=/web/start-ch.sh
PID=$(tail /tmp/cheyenne-8000.pid)

# Carry out specific functions when asked to by the system
case "$1" in
  start)
    echo "Starting Cheyenne "
    $STARTSCRIPT
    RETVAL=$?
    ;;
  stop)
    echo "Stopping Cheyenne"
    kill $PID
    RETVAL=$?
    ;;
  reload)
    echo "Reloading Cheyenne"
    kill -HUP $PID
    RETVAL=$?
    ;;
  reset)
    echo "Reseting Cheyenne"
    kill -USR1 $PID
    RETVAL=$?
    ;;
  restart)
    echo "Stopping Cheyenne"
    kill $PID
    echo "Starting Cheyenne"
    $STARTSCRIPT
    RETVAL=$?
    ;;
  *)

    echo "Usage: /etc/init.d/cheyenne {start|stop|reload|reset|restart}"
    exit 1
    ;;
esac

exit 0


(maybe it should be put on the wiki or into the repository to help 
other linux newbies)

(the last line should be:
exit $RETVAL
instead of:
 exit 0

Looks much better, thanks for your contribution, I'll copy/paste 
it on Cheyenne's wiki.

btw.. the /web/start-ch.sh looks like:
#!/bin/bash
cd /web/
./cheyenne &

I must use it because running cheyenne using full path like:
/web/cheyenne &

does not work as expected - it looks it does not gets the httpd.cfg 
file (probably)

hm.. maybe I could just skip to the directory in the init.d script.

yes.. it works:)

and the final init.d script is ?  :)

replaced $STARTSCRIPT with:
cd /web/
./cheyenne &

where the folder may be different so it's probably good to use it 
as variable

Kaj: so, this means that an install script would be required for 
Cheyenne to be able to run on UNIX, this is not something that I 
want for Cheyenne unless really necessary. Do you see any simple 
solution to that issue? If not, I'll revert it to write in /tmp by 
default and add a config option to let users choose alternative location 
when desired.

Hm, avoiding installers is good, so I guess a config option is readable

Packages for Linux package managers do indeed come with stuff to 
install into /var/

readable -> reasonable

If you want it, I can make the binary packages for deb, RPM and TGZ. 
 I already done it for Rebol, so it's easy for me. My email is [maxint-:-tiscali-:-it]

MaxV: thanks for the offer, but it's not required for now  as there's 
only one file to distribute (when encapped).

SVN revision 93:

o FEAT: new config keyword 'pid-dir for setting user-defined folder 
for Cheyenne's PID file.

o FEAT: Cheyenne's SVN global revision number now appended to Server 
response header.

o FIX: default location for %cheyenne.pid is reverted back to /tmp.

o FIX: PID file now takes the correct process uid:gid when Cheyenne 
is not run as root.

Nice

I'm able now to run Cheyenne as not-root, works ok so far, the only 
remaining issue is the first REBOL side process that stays as root 
(it's not a serious security threat anyway). I'll write a How-To 
for that in  the next days and will post it in the wiki (with Kaj's 
scripts also).

I take it we will still be able to run as root if we want to ?

Graham: sure

Thanks Doc, this is a really good feature for people who need greater 
security...


Chey.93 now running as user "www" rather than root on our new cloud 
server.

Great! :)

So, finally... it's time that I learn how to use the RSP API.

You've been running cgi ?

On apache, yes. On cheyenne, no.

CGI is nicer on Cheyenne because it acts like FastCGI for R2. But 
if you want to write your scripts in R3, you'll still need slow CGI 
instead of RSP

slow CGI ?

And switching away from root still doesn't work with Core

Traditional CGI, where you start a new process for each request

Cheyenne has to invoke the r3 interpreter ..?

If you want R3 scripts, how else?

send them to try rebol?

Then you'll be starting about three layers of shell processes - for 
security

Actually I wasn't aware that Cheyenne had a mechanism for external 
cgi .. but I guess it must

The only alternative would be implementing a continuous-running R3 
application server, instead of using the UniServe taskmaster server. 
But you'd still have the communication overhead between the processes

LNS server doing the cgi

RIS, I'd figure

call the r3.dll

Why?

so r2 can use R3

Sounds messy

anyway, what advantage would there to be use R3 over R2 for cgi ?