World: r3wp

like this 
dtach -A /tmp/mydtachsocket -z bash

yes, then you can hit Control - \ to disconnect, and dtach -a /tmp/mydtachsocket 
to reconnect

oh .. no dtach ...

what distro do you have? Debian?

Opensuse 10.0

I haven't used that. Does it use yum as package manager?

yast

wow .. it has a text gui :)s

yast can't find it ...

you could build it from source...it's documented on that page I linked

found a rpm, and it's working.  Thanks!

I have a problem with a CRON job. Running it by hand works, but it 
looks like it's not working if run via CRON.

How can I write some message to the system logfile from inside a 
shell script? Is there a command for this?

http://www.cyberciti.biz/tips/howto-linux-unix-write-to-syslog.html

Graham: I have no problem launching Cheyenne from ssh. I'm always 
using the binary version : ./cheyenne &

Your binary doesn't work on OpenSuse.  I get encapsulation errors.

That's strange. Can you show me what : ldd cheyenne returns ?

Btw, did you tried with : rebol -qws cheyenne.r & ?

hang on ... I have to login via putty

hmm.  didn't give me any message via ssh
here's ldd 
http://screencast.com/t/MnsrSebIz

ie. I ran ./cheyenne and just got nothing ....

If you're on Windows, you can use the SSH Secure Shell client for 
Windows (nice GUI) : http://charlotte.at.northwestern.edu/bef/SSH/SSHSecureShellClient-3.2.9.exe

Are you using sudo to launch cheyenne with root privileges ?

yes.

http://www.rebol.net/cgi-bin/rambo.r?id=4306&

I'm listening on port 8001

I got some error about being unable to write some .configuration 
file

I downloaded it twice in case it was corrupted.

And it works on Ubuntu JeOS

I won't be physically near that box now for a couple of days.  I'll 
test it again when I'm able.

Ok, when Cheyenne is started, it searches for a %httpd.cfg file in 
the same directory. If it doesn't find it, it writes down a default 
one. So if your cheyenne binary doesn't have the rights to write 
in its directory, that would the cause of the error.

oh no, it's quite a different file name ....

and httpd.cfg is present.

the file was of the form .xxxx.xxxx

Did you checked the rights needed to be able to write that configuration 
file ?

I was sudo ./cheyenne

So that's where you get encapsulation errors ?

yes, I think so.

It was 2 days ago and so I switched to using cheyenne.r instead

You can use Gab's workaround for that : write a small shell script 
that run cheyenne and run the script with sudo.

I will try ...

Gab says it causes the same problem on all unixes, but on ubuntu 
jeos, i don't get the encapsulation error.

maybe because you're logging as root ?

graham, you can also use "screen" if you want to be able to connect 
back and see the output. though, what you really need is just redirecting 
the input and output. rebol your-script.r >/dev/null </dev/null 2>/dev/null 
&

Tried again ...

./cheyenne - netstat says port 8001 is being listened, but I don't 
get any output using wget
sudo ./cheyenne - get the encapsulation error as you reported it
sudo rebol 
and then do %cheyenne.r works.

and wrapping it like ch.sh

#!/bin/sh 
./cheyenne &

sudo ./ch.sh

also works

not seeing this request to write a cofiguration file at present

I was installing ubuntu Jeos, and it seems to find the NICs, and 
gets the UTC time etc.  But when it starts up, ifconfig -a only shows 
the local loop adaptor.
And if I try and startup eth0, it says it doesn't exist.
Ideas?

Since Gutsy, the first couple of lines of /etc/iftab


# This file is no longer used and has been automatically replaced.

# See /etc/udev/rules.d/70-persistent-net.rules for more information.


The system for naming / managing eth0 eth1 has changed.  I had to 
mess a file in the path above to get my eth0 back.

oh gawd ...