Just ran my first milkyway WU. Noticed that it was outputting "progress" messages (presumably for debugging purposes). These milkyway messages were not helpful to me as an ordinary user. Besides, if several milkyway WUs were running simultaneously (this is a multi-core system), I would not be able to tell which task was putting out which message.

When the application gets to be out of "testing" satus, would you please eliminate such messages, or else explicitly write them to a file in the appropriate slots directory. I tend to look at "work flow" as it is happening - and extraneous messages just clutter up what BOINC is telling me. Thanks.
.

Could you post what messages you are getting, because I have yet to see any messages like this on the clients I've tested on.

Sorry, can't until I again download more WUs (I run off-line). What I do remember was messages that showed "how complete" (the percentage, to at least four decimal places).

[The way I often start the Linux client, I have stdout/stderr going to a terminal (instead of to a file). That is so that I can look at the messages scrolling by -- I tend to micro-manage BOINC. Besides BOINC internals and other projects, a contributor to message volume was me tracing http operations (seemed like some of the handshakes with the milkyway servers were initially failing -- but eventually these dialogues cleared up, and I did *not* spot any messages from BOINC communications that were other than ordinary). The result of how I was doing things - I don't have a permanent "log" of what I saw.]


I suspect you are not seeing any messages because your client is logging only to stdoutdae.txt/stderrdae.txt, whereas my client was redirecting everything to my display.
.