World: r3wp

Do must people run cheyenne from source or from its encap?

I ran my own encap version as I needed /command

and I didn't think the command license permitted me to run command 
on multiple servers

why not?

Irrelevant now

strange... this box runs this altme world, but not cheyenne.

meaning cheyenne won't run?

no, it's running. just no access

I see 8 instances of itself.  Is there some kind of setup required?

perhaps I need to uncomment the listen line in the config?

it defaults to port 80 ...

8 instances sounds right .. those are the worker processes

You only need the listen line if you are listening on a different 
port ... but did you install Apache ?

ie, did the distro you chose include Apache ...

anyway, you could try listening on a higher port and see if it works 
..

I know Henrik is using Linode and Cheyenne

no apache

firewall?

thinking.... does it need to run as root?

does wget work on localhost?

I've usually started cheyenne as root ...

there is no wget

read http://localhostfails

It's interesting... my browser hangs on it... so it's like it's not 
sending the http header to get things going.

I guess try root ...

must be a config problem. checking

tried 8000 too

netstat -an | grep "LISTEN"

( I'm reading from my own installation instructions :) )

needed root after all.

So, I wonder how to sandbox it on this server.

http://69.164.199.93

No known vulnerabilities ...

rotflol.

Anyway, got it running.  It reminds me of another product that comes 
as an exe only.

Maybe I learned something.  Anyway, good to finally run it on a linux 
box.

I just converted the home page to RSP.

dinner time

Doc, do you see any issues with that  on-message function I posted 
above?

If i put a "wait random 10" line within the do-task/on-done function. 
that returns an alert back to the page, then open a couple of browsers.. 
and fire the function in both, I get a lot of strange behaviour.. 
and I'm not convinced they don't block each other?

Carl, it needs to run as root to go below port 1024.

I see you have it running. :-)

Except it would not run for him on port 8000

Carl, it's possible to SU to any user while started as root, but 
that will only work for the processes forked, not the first one (the 
Cheyenne/Uniserve main process). In config file, just uncomment those 
lines, choose the adequate user/group targets and restart the server 
:

	;	user  nobody
	;	group nobody


I need to investiguate more in Apache's sources to see how they achieve 
full SU on all processes.

Terry: on-message function => yes, loading a script on each request 
is ok for debugging, but bad pratice for production. I'm not sure 
that WAIT is safe in Cheyenne callbacks, never tested that, this 
function is not supposed to be used in user code inside Cheyenne 
main process (it would work in a RSP script, but will block valuable 
resources and reduce scalability).

You should try with a timer event instead (if you really need to 
delay it server-side).

Carl, good to hear you trying out Cheyenne 8-)  now you know why 
we need threading in R3 to replace the worker processes.

BTW, I see you are running version 0.9.19 which is a bit old, I really 
suggest you dowload latest SVN from here:
  svn checkout http://cheyenne-server.googlecode.com/svn/trunk/
I personally run it from source. W la Rebolution!

Will: thanks for the info. We can update to it.

Doc: if there's any small thing we can do on our side in 2.7.8 to 
help with SU situation, let me know.  As you know, running the server 
as SU will be a problem for many folks.

Thanks Carl, I'll investiguate that and will send a report of requirements 
to BrianH if necessary.