A better way might be to track the log-file itself and look for particular log messages. This could be used to both deterimine when :8888 is available, and also to spot common problems.
Ian. On Wed, Jan 22, 2003 at 11:58:18AM -0000, Dave Hooper wrote: > > hi there, > > > > i just found a bug that fucked me up the ass for the last two days. > > if you enter a non-existent hostname in the allowedHosts field, the > > freenetnode crashes with a BadHostName exception, but does not indicate > > this > > on the system tray (windows). > > See my earlier email. I'm currently modifying the windows tray app to > probe the FNP (FreeNet Protocol) and web interface ports to see if the > freenet node is actually running. This will visually indicate precisely > this sort of problem. > As general advice, if you're having problems with freenet and it seems > like it isn't working as it should, you can right click the tray and pick > View Logfile to see the most recent logs which should include errors and > exceptions. Alternatively use the 'most recent exceptions' (I forget its > name) in the web interface. > > Can you describe the 'crash' ? Does the web interface actually stop > working? Does the BadHostName exception actually not appear in > freenet.log (as shown by View Logfile) ? > > d > > _______________________________________________ > support mailing list > [EMAIL PROTECTED] > http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support -- Ian Clarke ian@[freenetproject.org|locut.us|cematics.com] Latest Project http://locut.us/ Personal Homepage http://locut.us/ian/ _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
