addition, the core client can write a variety of 'logging' messages. The logging options are read from a file log_flags.xml. This file has the following format: ".html_text(" [ flags ] ")." The flags are as follows: "; list_start(); list_item_func("", "Log the start, restart and completion of computational tasks." ); list_item_func("", " Log the start, restart and completion of file transfers. " ); list_item_func("", " Log connections with scheduling servers. " ); list_item_func("", " Log changes to the 'client state' data structures. " ); list_item_func("", " Log debugging information about task execution. " ); list_item_func("", " Log debugging information about file transfers. " ); list_item_func("", " Log the request and reply messages of exchanges with scheduling servers. " ); list_item_func("", " Log debugging information about HTTP operations. " ); list_item_func("", " Log debugging information about HTTP proxy operations. " ); list_item_func("", " Log the passage of time. " ); list_item_func("", " Log debugging information about network communication. " ); list_item_func("", " Log debugging information about measurements of CPU speed, platform, disk space, etc. " ); list_item_func("", " Show what poll functions do" ); list_item_func("", " Log debugging information about the GUI RPC interface. " ); list_item_func("", " Log debugging information about the CPU scheduler. " ); list_item_func("", " Log debugging information about the screen saver. " ); list_item_func("", " Don't check file sizes" ); list_end(); page_tail(); ?>