Shibboleth Developers

["Mark Wilcox" <>]

Based on my experiences with WebCT Vista which uses log4j as well, 100MB is
about right. It's big enough that you get a pretty good audit trail if you
have to trace back when stuff started to go south and anything bigger & it
really isn't useful unless you've got some type of audit requirement to keep
all logs.

Mark

> -----Original Message-----
> From: Walter Hoehn 
> [mailto:]
> Sent: Wednesday, May 12, 2004 11:08 AM
> To: 
> 
> Cc: Noah Levitt; 
> 
> Subject: Re: shib origin ok, log files rolling over ok.....
> 
> We can make this whatever we want.  The point is to do something that
> is reasonable for most production deployments.  Right now we keep 100MB
> of logs.  I'm not sure where the sweet spot is, but I'd definitely want
> more than 20 MB.  Anyone who has an opinion on this should speak up
> before we release...
> 
> -Walter
> 
> 
> On May 12, 2004, at 8:22 AM, 
> 
>  wrote:
> 
> > At 3:19 PM -0500 5/10/04, Walter Hoehn wrote:
> >> Well, you can have any setup you want by manually configuring log4j.
> >> The point of the logging auto-setup stuff isn't to have lots of
> >> configuration options, log4j already has that, it is to handle the
> >> generic case as close to out of the box as possible.
> >>
> >
> > any chance we could default this number to something like 10, or 14,
> > instead of 50?
> >
> > ....OTOH, if this number is hardwired somewhere deep in the guts of
> > log4j, forget it.......