Step by step for pproxy installation?

[Russ]

I'd like to set it up on the Linux box and map the nodes on the rack to it. Reading through the FAQ's at dnet all I find are answers to questions that would arise after installation.

Where is the installation info?

Russ, NCNE

 

[SocrPlyr]

Russ, there is none (i tried and couldn't get it working right)
i gave up hope you have better luck.

 

[Kilowatt]

Russ and others,
Most of the Configuration settings are explaned (although not to well) in the Readme file that comes with the PProxy.

In Linux, it should be in the Docs folder where you put the PProxy after un-tarballing it.

I don't have one running on a Linux box at the moment, I use the same W2K box as my Networking Router, for Dnet Proxy & my little HTML generating Stats Page.

I can give you a run down on all that you'll need, just look at the PProxy.ini below.

All that you'll need to change will be highlited in Bold
=====================================
; $Id: proxyper.ini,v 1.20 2000/01/23 15:49:16 jlawson Exp $

[KeyServer]
ipaddress=us.v27.distributed.net
port=2064
connectperiod=600
connectivity=normal ; normal,offline,lurk,lurkonly
;bindip= ; IP to talk out to keyserver from
;uuehttpmode=0
; 0=normal,1=uue,2=http,3=http+uue
; 4=socks4,5=socks5,6=genproxy,7=genproxy+uue
;httpproxy=wwwproxy.corporation.com
;httpport=8080
;httpid=

[ports]
;listenaddress= ; IP to accept clients on
port=2064
;port2=23 ; must be root for ports < 1000
;port3=80
testport=3064
timeout=30

[console]
logfileconsole=Whatever you want your main .log named
logfileconsolerotation=daily or weekly,yearly
consoleverbosity=&quot;general stats keyblock server client buffers timestamp attention errlow errsevere&quot;
timestampflags=129 ; 129=utc-2, 1=lt-2, 130=utc-4, 2=lt-4

[rc564]
logfilekeyblock==Whatever you want your stats .log named
logfilekeyblockrotation=daily] or weekly,yearly
minkeysready=5000 as big as your herd is, I'd go at least 10,000
maxkeysready=5001 10,001
maxkeysdone=2000

[desII]Who Cares, as long as it says contestclosed=1 at the end
logfilekeyblock=pproxydes
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3
contestclosed=1

[ogr]Who Cares, as long as it says contestclosed=1 at the end
logfilekeyblock=pproxyogr
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3
contestclosed=1

[csc] Who Cares, as long as it says contestclosed=1 at the end
logfilekeyblock=pproxycsc
logfilekeyblockrotation=daily
minkeysready=10
maxkeysready=20
maxkeysdone=3
contestclosed=1

[misc]
proxymessage=&quot;Kilowatt's Stats Proxy!&quot; Your own clever saying here, between the &quot;&quot;s
pidfile=rc5desproxy.pid
statusperiod=3600 this is a 1 hour period, to cut down on file size
;logfilecompressor=logcompressor.sh

[ignoredip]

[allowedip]
==============================

EDIT- You don't need to set the IP in the PProxy, just aim all the clients to the Linux box's IP, and it should work.

When setting the inbuffer, figure about 1 block per CPU Mhz per day.
Then multiply it by at least 3 day worth, incase something happens you can't get online, or dnet goes down for a few days.

I flush anywhere from 5-7000+ a day, an have mine set to 20,000 in, and flush every 2500.

Does that help?

 

[Russ]

Killowatt,

That helps bunches. And your timing is excellent. I just got done unzipping the tar ball and was reading the readme while trying to figure out the settings in the ini file.

One question that occurs, though. When pointing my clients at the server, don't I have to make an entry somewhere in them for the directory that the pproxy is located in? Otherwise, how do they know where to look once they get past the IP address? It's in /root/proxy.

Russ, NCNE

 

[Russ]

HMM. Well, I just fired it up, and it connected to dnet no problem and promptly proceeded to stock up on OGR BLOCKS! I put the contestclosed=1 setting in the ini, but it still wants to do them. Can I just delete the entire stupid section?

Russ, NCNE

 

[Russ]

I see what happened with that. The keyserver had a message that said &quot;OGR is now open&quot; and automatically changed the entry to 0 in the ini file. What crap is this?

Anybody know how to tell the keyserver to leave my ini file alone?

Russ, NCNE

 

[Sloth]

As I understand it there is nothing you can do to kill a contest on the proxy. If you set it to closed the next time it connects to dnet it is updated as being open.

You can set the buffer size to zero though. This will keep you from picking up the blocks.


S.

 

[Russ]

I'LL BE DAMNED! It's working!!!!!!! I just connected the first node, and sure enough it grabbed some work and said:

&quot;TA Cube Pproxy!&quot;

YEEHHHAAAWWWWW!!!!!!

Russ, NCNE

 

[Kilowatt]

Russ, You just need to tell your clients to use the Linux Box IP, and to connect on port 2064 (generic).

You don't need to tell the clients where the DIR is on the Linux Box.
It's a Network Thing!

I take it your still using Two disks to boot the Rack nodes.
You're not booting to NFS are you? Each floppy has it's own Kernel?

<<Man, I'm half tempted to Use these 5 BP6 boards, and 10 Cel 500's to build my own rack.
It sound like a bunch of frustratio.....Err...Fun!>>

If you didn't change the [OGR] configuration, ie:

minkeysready=10
maxkeysready=20
maxkeysdone=3

You only downloaded 20 Blocks of that nasty OGR stuff.

While your changing your clients over to your PProxy, make sure they all have:
[misc]
project-priority=RC5,DES=0,CSC=0,OGR=0

Edit- DOHH, I'm to late!

 

[Russ]

HeHe. Thanks for all the help, kilowatt! Yep, using two disks. The first is Freesco to bootup each node. Then mount the dnet disk and run the client. I had already changed the ini on all the floppies to RC5 first, and 0's for all the rest of the projects.

Now, I just need to edit the rest of the disks to reflect the IP of the server.

Now, how do I SEE what's going on on the server. How many blocks are buffered? how much has been done? etc, etc.

Russ, NCNE

 

[Kilowatt]

Just go to your /root/proxy folder (you'll probably have to be root, since that's where you put it)
And look at the Whatever you named your main .log file.

You could use a Term box on your server, and type tail -f /root/proxy/Whatever you named it.log'.
You'll need a space after /proxy/, it keep closing it up here in the forums.

<<hehe>> I'll give you the rest of the night off, to rest up before helping you with your own stats deal on your Linux Box.