> > Now my freenet is running on my fit-pc - has been running properly > > the last week. > > > > I did following (I am using ubuntu 8.04): > > > > 1. Created a text file /etc/cron.allow containing my username. > > That might explain why your wrapper's wrapper (your crontab-run script) > wasn't working. Though you don't have to manually specify a cron.allow > file... you can just delete it, and it allows everyone by default, > unless they're mentioned in cron.deny. > > > 2. Inserted following line in /etc/crontab: > > > > @hourly myusername ~/Freenet/run.sh start > > > > (Probably not necessary) > > This one, the system-cron file, is necessary. The second one is > useless, I believe. Cron never checks ~/.crontab--only /etc/crontab, > and /var/spool/cron/crontabs, for individual users. > > > 3. Created a text file ~/.crontab with the following line: > > > > @hourly myusername ~/Freenet/run.sh start > > > > The freenet system seems however to very sensitive, and stops when I > > do some other work, and then I have to restart freenet, but as a > > mini-freenet server just serving data, it seems to work well. > > Interesting. And bad! :). How sure are you that the crashes occur when > you're doing other work on the system?
Ok, not so sure, just tried again and freenet did not stop this time. > (Is it wishful thinking? ;). > What is the "nice" value for freenet's java process? It is 10 > (You can check > it via the "top" command.) I had mine at a brutal 20 (the lowest > priority of all my processes on my system), and toad suggested that > this may have been the cause of my crashes. I have raised it's priority > now, and will continue to test. Though I am skeptical. Crashing should > not happen. Ever! > > > Thanks everybody so far, for your help > > "So far". I'm sure we haven't heard the end of this one :).
