OK. I changed this line: $JAVA $VMARGS -jar ofbiz.jar $* >>$OFBIZ_LOG 2>>$OFBIZ_LOG& to $JAVA $VMARGS -jar ofbiz.jar $* >>/dev/null 2>>/dev/null&
Not sure why OFBIZ_LOG is listed twice, but I'm no shell script guru. ----- Original Message ----- From: "Jonathon -- Improov" <[EMAIL PROTECTED]> To: user@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. Moreover, debug messages shouldn't be done with System.out.println. Jonathon [EMAIL PROTECTED] wrote: > Vince > > It is my view that a production server of any sort should never redirect > stdout and stderr to a log file because you have no control over it. If you > want stdout and stderr, it's fairly simple in java to catch it and write it > to a rotating log file. In Ofbiz's case, not everything that goes to stdout > and stderr 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 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 to be redundant with ofbiz.log. console.log is not rotated, so it > gets very large. > Should we use the first option and send everything to /dev/null? > > Vince Clark > Global Era > The Freedom of Open Source > [EMAIL PROTECTED] > (303) 493-6723 > > >
