What i means is, launchd loaded this com.freenet.start.plist item and tried to carry out what it requests. Launchd items normally stay loaded and start the program in question in response to events or demand, or in some cases, they are supposed to keep the program running even if it quits or crashes. What appears to be happening is launchd starts the run.sh script, which starts freenet and exits, causing launchd to think it quit and try all over again. The LoadOnlyOnce key is supposed to prevent that from happening, so why it would even try again is puzzling to me. As i said i'll have to do some tests, but for now delete the plist item and start freenet manually.
On Mon, Jun 8, 2009 at 3:03 PM, Mel Charters <[email protected]>wrote: > Steve, > Freenet starts and runs correctly when started with "sh run.sh start" > in Terminal. I don't understand the console log terminology > "respawning to quickly!"? Could it be a problem with the slow > processor, it is 667 Mhz.? > > Incidentally, when I try to stop using "sh run.sh stop" in terminal > it appears to just kill the pid, whereas if I shutdown the node in > browser (Firefox) it seems to close files in an orderly manner. > > > Mel Charters > _______________________________________________ > Support mailing list > [email protected] > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:[email protected]?subject=unsubscribe >
_______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[email protected]?subject=unsubscribe
