"Dave Hooper" <[EMAIL PROTECTED]> writes: > 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.
It's really easy to add logger hooks so that specific logging information gets sent in a specific format to the systray app. > 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" ...) > It'd really hard for fred to die (the only case I know being internal JVM errors) without catching the exception and at least using its built-in exception handler. I'd give the developers some credit and try parsing logs. > Probing FNP and fproxy ports is the obvious solution. > > d > This could be done as well, but I think much better info can be had from the logs. Although... One could execute the FCP command to get info from the node, and use that info for some sort of (very-) mini status. Thelema -- E-mail: [EMAIL PROTECTED] Raabu and Piisu GPG 1024D/36352AAB fpr:756D F615 B4F3 BFFC 02C7 84B7 D8D7 6ECE 3635 2AAB _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
