[freenet-support] HOWTO start up FREENET automaticly with Runlevel Scripts - The DIRTY solution...
ok i got it now! Was a darn birth but at least it works quick n dirty. You
GURUs out there will LAUGH about it! :) but it took a while for me to get
this crap working. All those SHELLS and Levels and PATH Variables which are
never are the same...argh!..confusing me :) SO here my dirty solution for
dummies like me and anybody with the same problem:
My System is a SuSE 9.0 Pro Linux. Target is to install and config FREENET the
way that it will start up automaticly at System-Boot time using RUNLEVEL
Scripts.
Things to do:
1. make sure you solve the software requirement für the freenet software (e.g.
JAVA JRE)
2. Install FREENET (unpack it somewhere) e.g. /freenet
3. edit the included Freenet START-Script and insert these two lines at the
beginning:
~
#!/bin/sh
export PATH=$PATH:/usr/lib/SunJava2-1.4.2/jre/bin/ NEW LINE
TO INSERT!
cd /
freenet
NEW LINE TO INSERT!
# Check to see whether we use echo -n or echo \c to suppress newlines.
.
.
.
~
1st Line will extent the PATH enviroment Variable to inclusde the JAVA
executables. This is why ever, NOT default in the SuSE 9.0 distribution!
2nd Line just changes PWD to freenet home. seems freenet and java needs that
to find anything.
4. create a new RUNLEVEL scriptfile
(e.g. 'cp /etc/init.d/skeleton /etc/init.d/freenet)
5. edit this file and make it look like this:
#! /bin/sh
#
# /etc/init.d/freenet
# and its installation under /freenet
#
### BEGIN INIT INFO
# Provides: freenet
# Required-Start: $local_fs $remote_fs $network
# Required-Stop: $local_fs $remote_fs $network
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: freenetproject.org node/proxy software
### END INIT INFO
case $1 in
start)
echo -n Starting freenet
sh /freenet/start-freenet.sh
;;
stop)
echo -n Shutting down freenet
sh /freenet/stop-freenet.sh
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start
;;
*)
echo Usage: $0 {start|stop|restart}
exit 1
;;
esac
6. let chkconfig start the script at the default runlevels for network
services 3+5 by entering chkconfig freenet on
That should be all to do!
Hope it will work for you too!
greets
Axel
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]
[freenet-support] Re: HOWTO start up FREENET automaticly with Runlevel Scripts - The DIRTY solution...
Axel Werner writes: ok i got it now! Was a darn birth but at least it works quick n dirty. You Been there, done that. :) 1st Line will extent the PATH enviroment Variable to inclusde the JAVA executables. This is why ever, NOT default in the SuSE 9.0 distribution! Blame Sun, their RPMs are pretty awful. That's why I use jpackage.org's JRE/SDK RPMs. You'll need to rebuild them due to licensing issues, but they're much more refined that Sun's own. plugThey also work well with with my own Freenet RPMs (available at http://nightwatch.mine.nu/freenet/)/plug 2nd Line just changes PWD to freenet home. seems freenet and java needs that to find anything. Java doesn't mind being in a different directory as long as freenet.jar and freenet-ext.jar are somewhere in the classpath. Freenet's default config files and startup scripts do assume that everything is in the current working directory. Of course, you can override the default paths in the configuration file and use java freenet.node.Main -p /path/to/freenet.conf to start the node. -- Mika Hirvonen [EMAIL PROTECTED] http://nightwatch.mine.nu/ ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] RE: trouble getting any information
On Mon, Jun 28, 2004 at 07:52:10PM -0400, [EMAIL PROTECTED] wrote: I am running Win XP with IE and Zonealarm Pro (active and switched off, no difference). Please don't use IE with Freenet. You don't want to compromise your anonymity, whether you now feel you need it or not. As for the problem you describe, it may be that you just need to keep running Freenet. When I've gotten those messages (and everything should have been okay) I've noticed that they just go away after a while. A small possibility is that everything *is* running okay, but your node doesn't know about enough other nodes yet, and the few it does know about maybe rejected your node's advances because they were too busy at the moment. Like a busy signal on the telephone. Remember also that Freenet, unlike other peer to peer networks, doesn't offer the convenience of turning it on only when you want. For the node to work at all well, it needs to integrate itself into the network. On the other hand, Freenet should be more sustainable in the long term as it really penalizes leaches, and requires a medium term commitment of resources. When I started my last office job, I learned everyone's name and got on a conversation-basis with them sometime before I actually was able to get in on the rumor distribution chain. It's roughly the same (in effect) with Freenet. Right. The node has to learn about the other nodes, as well as finding more nodes to talk to. Also there are initial problems with connecting to other nodes. Run it as much as possible until you can reliably retrieve a few sites. You don't need to actually USE it much; it should learn by itself. You can encourage this process by trying to browse sites, or installing Frost (http://jtcfrost.sf.net/). On the other hand, maybe there's a config problem? Maybe try re-seeding the node, by running freenet-webinstall.exe again. -todd -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] debian packages
hi, there are debian packages for freenet which are stupid old. If there is a debian support, then they should be updated once a months. I know there is a update.sh script. But most debian users want to use there apt-get. 1)Perhaps, if the packages-maintainer would build a little script around the update.sh to build a new packages every time a new build comes out, it would make a much better look for debian users. 2)Rename it freenet-installer and give it a seperate version-number. 3)Or just delete freenet-packages from debian. I think no package is better then a old package. bye ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Do stable unstable nodes share the same seednodes.ref?
Just wondering if the stable unstable nodes share the same seednodes.ref? If yes, then what divides the stable and unstable network? -- Best regards, Weiliang Zhang Department of Computing Imperial College London, UK ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Do stable unstable nodes share the same seednodes.ref?
Weiliang Zhang wrote: Just wondering if the stable unstable nodes share the same seednodes.ref? If yes, then what divides the stable and unstable network? 1) no which infers 2) black magic. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
