Ian Clarke wrote: > 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.
I disagree - I think we had this discussion before. A user can review the log-file if he/she wishes, but programmatically parsing the log-file is not really sensible, unless we are able to guarantee the text, content and meaning of messages will not change beyond a rigid specification. One way to tackle this might be to add ftp-style codes to error messages, but it still doesn't solve the issue of needing to identify when something has *stopped* working (if it's stopped working unexpectedly it won't be able to log a message saying "I've stopped working unexpectedly" ...) Probing FNP and fproxy ports is the obvious solution. d _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
