On Jul 7, 2005, at 7:47 PM, Aaron Mulder wrote:
On Thu, 7 Jul 2005, Geir Magnusson Jr. wrote:
How do I get progress bar *and* log level DEBUG?
That doesn't make sense to me -- the DEBUG output would mangle the
progress bar by inserting output between every time the progress
bar tries
to repaint its progress line. Besides resulting in tons of separate
progress lines, since the progress bar doesn't emit carriage
returns while
rendering, I think the first debug message after a repaint is
appended to
the end of the progress line instead of starting a line of its own.
Finally, the status information provided by the progress bar is
more or
less duplicated by log messages announcing as each component is
started.
I see. Ok. I'l admit I hadn't tried it, but was going on what you
had posted to the list.
I had figured that the debug output was going to a logfile, and the
progress bar was on the console ('stdout'), so a human could see the
progress coming up, and still have the full record in the log. You
could also print the current progress bar into the log at each update
point, so people could put two and two together, so to speak...
If we were willing and able to eliminate all DEBUG and INFO output
from the server startup sequence, we could keep the progress and
still get
the DEBUG or INFO messages after startup. However, I think that's
unlikely. For example, I got ActiveMQ to agree not to emit a WARN
message
if the necessary JMS tables are already available at startup, but it
didn't sound like they were prepared to forego that message entirely.
Yah - I think we definitely need to have all info available for
people, but the progress bar idea is cool too...
geir
Aaron
On Jul 7, 2005, at 7:25 PM, Aaron Mulder wrote:
Okay, so based on this feedback thread,
- I'll change "-noprogress" to "-quiet"
- I'll leave "-v" and "-vv"
I think that's the best combination too. Being lazy myself, I'm
not ready for 2-3 large command line args to achieve "-v". :)
Thanks,
Aaron
On Wed, 6 Jul 2005, Matt Hogstrom wrote:
+1 on the format.
I think I like -quite instead of -noprogress...not sure if this
has been posted already.
- Matt
----- Original Message -----
From: "Jeff Genender" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, July 05, 2005 11:19 PM
Subject: Re: New Startup Output, Mark 2
Nice! You rock!
Aaron Mulder wrote:
Okay, now you have the following options:
java -jar server.jar -noprogress Very quiet startup, log level
WARN
java -jar server.jar Progress bar, server version,
etc.
java -jar server.jar -v No progress, log level INFO
java -jar server.jar -vv No progress, log level DEBUG
The server version printed will be not too useful for developer
builds, but should be meaningful for snapshots, milestones, and
official
releases.
Aaron
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
