yeah the BadHostName exception is in the logfile (thats how i found out of 
course..).
the web interface does not start up.

On Wednesday 22 January 2003 11:58, 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


_______________________________________________
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support

Reply via email to