: Re: managing the size of console.log
Skip,
Agreed. I usually redirect console.log to dev null (discard).
Log4J in OFBiz does capture output in rotated logs, so the console.log is just extra. Moreover,
debug messages shouldn't be done with System.out.println.
Jonathon
[EMAIL PROTECTED
@ofbiz.apache.org
Sent: Tuesday, December 4, 2007 10:22:14 PM (GMT-0700) America/Denver
Subject: Re: managing the size of console.log
Skip,
Agreed. I usually redirect console.log to dev null (discard).
Log4J in OFBiz does capture output in rotated logs, so the console.log is just
extra
There are two startup options in startofbiz.sh
# start ofbiz
$JAVA $VMARGS -jar ofbiz.jar $* $OFBIZ_LOG 2$OFBIZ_LOG
#exec $JAVA $VMARGS -jar ofbiz.jar $@
We are using the first option, which logs everything to console.log. This
appears to be redundant with ofbiz.log. console.log is not
just comment out the redirect to the log.
there are plenty of other logs to look at.
rem $JAVA $VMARGS -jar ofbiz.jar $* $OFBIZ_LOG 2$OFBIZ_LOG
$JAVA $VMARGS -jar ofbiz.jar
Vince M. Clark sent the following on 12/4/2007 12:58 PM:
There are two startup options in startofbiz.sh
# start ofbiz
You may also have a look at the colored log in webtools
Jacques
De : BJ Freeman [EMAIL PROTECTED]
just comment out the redirect to the log.
there are plenty of other logs to look at.
rem $JAVA $VMARGS -jar ofbiz.jar $* $OFBIZ_LOG 2$OFBIZ_LOG
$JAVA $VMARGS -jar ofbiz.jar
Vince M. Clark sent
To: user
Subject: managing the size of console.log
There are two startup options in startofbiz.sh
# start ofbiz
$JAVA $VMARGS -jar ofbiz.jar $* $OFBIZ_LOG 2$OFBIZ_LOG
#exec $JAVA $VMARGS -jar ofbiz.jar $@
We are using the first option, which logs everything to console.log. This
appears
is written to ofbiz.log, but everything of importance is (in my limited
experience). console.log is only useful in my view during developement.
Skip
-Original Message-
From: Vince M. Clark [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 04, 2007 12:58 PM
To: user
Subject: managing the size
