Hi Dirk, Got it. Silly me, wasn't paying enough attention to the console running basexhttp while fiddling around. Thought it wouldn't be logged but it is. Duh.
--Marc On Sun, Aug 10, 2014 at 6:19 PM, Dirk Kirsten <d...@basex.org> wrote: > Hello Marc, > > The BaseX log only logs this HTTP requests and other internal stuff, as > you correctly observed. > As said in the documentation, the trace is sent to stderr, i.e. you can > redirect the standard error using normal unix tools. Starting basexhttp > like that > > basexhttp 2> error.log > > will log all errors to the file error.log > > Cheers, > Dirk > > On 10/08/14 18:09, Marc van Grootel wrote: > > Hi, > > > > I used fn:trace in code and I made sure it is not optimized away. Saw the > > trace msg in the gui. But when doing it via the http server only the > > standard request info is shown in the log > > > > 18:05:47.810 0:0:0:0:0:0:0:1:50364 admin REQUEST [GET] > > http://localhost:8984/ > > 18:05:49.234 0:0:0:0:0:0:0:1:50364 admin 200 REQUEST 1463.52 ms > > 18:05:49.235 0:0:0:0:0:0:0:1:50364 admin 200 0.32 ms > > > > The docs say that trace is sent to stderr, isn't that logged? > > > > Is there a way to turn the logging volume for http server logging up a > > notch or is there some other way to get the trace messages logged? > > > > -- > Dirk Kirsten, BaseX GmbH, http://basex.org > |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz > |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: > | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle > `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22 > -- --Marc
