This is the mail archive of the mailing list for the frysk project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: getLogger parameter

Hi Andrew,

On Thu, 2006-09-07 at 16:47 -0400, Andrew Cagney wrote:
> > On Wed, 2006-08-16 at 15:14 -0400, Andrew Cagney wrote:
> >> I've changed all the calls to getLogger() so that they specify the 
> >> current package (e.g., frysk.event, frysk.proc, frysk.gui.monitor), and 
> >> not frysk .Config .FRYSK_LOG_ID.  My understanding of the logging code 
> >> is that's the general intent as it makes possible fine-grained logging 
> >> such as just frysk.event,
> >
> > Can you explain this a little more? I am trying to get log output for
> > the loggers in Task and TaskState with TestRunner. These used to show up
> > with ./TestRunner -c FINE or ./TestRunner -c FINEST, but now these only
> > give output for Wait and EventLoop, but not for anything else it seems.
> > Is there some new magic incantation to get the log output for other
> > classes?
> >   
> There shouldn't be a new magic incarnation.  -c manipulates the top 
> level "frysk" logger and that in turn should manipulate all "frysk.*" 
> sub-loggers (unless I've misunderstood this).

But how does it work? How do you get log output for say Task and
TaskState when using TestRunner now?

I reverted to using System.err.println() for now, but at times it would
be nice to get the log output as before this change.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]