Sascha Noyes ([EMAIL PROTECTED]) wrote: > when i run ./preconfig.sh, i get a freenet.conf file with 3 lines: > > ipAddress=localhost.localdomain > listenPort=19871 > seedNodes=seednodes.ref
Ick! Then don't do that. It's clearly broken. > however if i run start-freenet.sh without the --config switch (seeing as i > already ran preconfig.sh it doesnt print that i should run start-freenet.sh > with the --cofig switch) freenet seems to start up normally, but this is what > is printed in the log file: > [...] > Sep 5, 2002 9:35:25 AM (freenet.node.Main, main): Failed to load service: > fproxy > freenet.interfaces.ServiceException: No class given Your config file is incomplete. > Sep 5, 2002 9:35:26 AM (freenet.node.Main, main): Cannot announce with no seed > nodes! And you have no seed nodes. :( > there are indeed no seed nodes in todays seednodes.ref file. Ouch. Get one from someone else, then. Mine (not *terribly* recent, but it should be usable) is at <http://wooledge.org/~greg/seednodes.ref>. Or use google to find others. (I hope there *are* some others.) > maybe someone would care to send me their freenet.conf file? (You sent this message only to me, not to the support list.) You probably don't want that. What we need is good documentation for this stuff, because it's obvious that whatever you were reading is full of shit. (Or there are major bugs in the scripts you were running.) Here's what you should do to get Freenet working on a Unix-like system: 0) Decide how big your data store will be. 1) Install a Java VM. 2) Create a "freenet" user account and make its home directory reside on a file system with enough space for the data store and some big logs. Do all the rest of this as the "freenet" user. 3) Download the freenet-ext.jar and freenet.jar and seednodes.ref files. The seednodes.ref can come from anywhere, not necessarily freenetproject.org. The freenet.jar file is actually named freenet-latest.jar on the snapshots page; rename it or symlink it. 4) export CLASSPATH=$HOME/freenet.jar:$HOME/freenet-ext.jar java freenet.node.Main --config 5) Customize the freenet.conf file that was just created. 6) Enable port forwarding on your firewall if needed. 7) Set any additional environment variables or ulimit commands or umask commands, etc., that may be necessary in your environment (e.g., ulimit -n 128; ulimit -d 262144). 8) Determine if any additional arguments are needed for your Java VM to run a node successfully (e.g., -mx 256M). 9) nohup java [additional args] freenet.node.Main & When you're happy & comfy with the results, customize your freenet user's dot-files, or write some run scripts, or set up cron jobs, or set up boot scripts to start the node at system boot time, or whatever. :-) I don't have any files named *.sh in my freenet user's directory. Based on what you've just told me, I'm glad I don't. -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] | - The Red Hot Chili Peppers http://wooledge.org/~greg/ |
msg01082/pgp00000.pgp
Description: PGP signature
