RE: {bb} how can ftp be an "unknown directive"?

["Jasper Filon" <jasper.filon@ritstele.com>]

Big brother uses Telnet to send messages from the client to the server. Basicly, is does:
"
telnet <BBDISPLAY> 1984
stats server.test <colour> <some other usefull information>
q
"

>From the client, you should be able to do (if telnet installed):
telnet <BBDISPLAY> 1984

It should open an connection, witch will be closed by BB after a few second. If you get a connection time out, then the purples are logical, because the client can't reacht the server. In this case, check if there is some kind of conectivity by doing a ping test and check firewall settings and stuff like that.

Kind regards,

Jasper

-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com]On Behalf Of Francis
Hwang
Sent: vrijdag 4 juni 2004 17:40
To: bb@bb4.com
Subject: Re: {bb} how can ftp be an "unknown directive"?


There's only the one line. This is a very basic setup, with the same 
machine serving as server/display/client.

What happens more generally is that I start up the BB server and it 
seems to run okay. The web page shows that the status page is updated 
once after I start the server, with all the services purple, which to 
my understanding is what should happen if there are no clients running. 
bb/BBOUT has these occasional lines like

Fri Jun  4 08:07:23 2004 bb CONNECTION TO 66.240.185.230 TIMED OUT...
Fri Jun  4 08:10:27 2004 bb CAN'T CONNECT TO bbd SERVER @ 66.240.185.230

but from perusing the list archives it seems like these sometimes "just 
happen" and can be ignored.

Then, when I start up the client, bbc/BBOUT looks like this:

Fri Jun  4 08:34:35 2004 bb-local.sh Fri Jun  4 08:34:35 2004 bb 
CONNECTION TO 66.240.185.230 TIMED OUT...
Fri Jun  4 08:37:39 2004 bb-local.sh Fri Jun  4 08:37:39 2004 bb CAN'T 
CONNECT TO bbd SERVER @ 66.240.185.230

I don't know if these are to be expected in the client's log file. At 
any rate, the BB web page never updates.

Over on this page ( http://support.bb4.com/archive/200105/msg00066.html 
) I found a reference to being able to telnet to port 1984 ... I can 
see port 1984 is open when I run "netstat -a", but can't telnet to it. 
Does that matter? I have to confess that I'm unclear as to how telnet 
is related to BB in the first place.

Thanks,
Francis




On Jun 3, 2004, at 5:45 PM, Philip Clark wrote:

> On Thu, 2004-06-03 at 22:28, Francis Hwang wrote:
>> I checked in bb/etc/bb-server.sh and I found the BBNETSVCS line with
>> "ftp" in it. (I'm using 1.9e, btw). And as per Phil's comments, I
>> checked the files, but they'd been edited in emacs anyway and seem to
>> be fine.
>
> Emacs should be well behaved. Is bbchkhosts.sh only complaining about
> that one hosts line? Is there anything that might be significant about
> that line? It might help to show that ones that come before and after.
>
>> Any other ideas, or places in the docs you can recommend I read up on?
>
> My first instinct would be to note the information down and then
> delete the line that is causing the problem. Then add it back to
> see if the problem re-occurs.
>
> The list archives are probably the best source of information for
> something like this.
>
> Cheers, Phil.
>
>
>
> -- 
> The most dangerous thing in the combat zone is an officer with a map.
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message.
>

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.