>>>>> On Fri, 29 Jul 2011 09:23:20 +0200, Annette Jaekel said: > > Hello, I'm occupied with some performance issues regarding to my backups. I > set debug=20 and trace=1 within bconsole for a client and a storage daemon > and traced some messages from the daemons within tests. Everything work. But > nothing traced then to the corresponding files within last nigthly backups. > > So my first question is: If I setup trace mode within bconsole, is this a > permanent setting or is it only for the console session (that i closed after > trace/debug setting and my tests).
It should be permanent. The status client command reports the level in the client. Have you tried a higher debug level? > Furthermore: Is there anywhere a detailed (!) documentation about debug or > trace mode? For example for the different debug levels or the interpretation > of output? I only found a hint about levels: Set it to 20, for more info to > 60, for a lot of infos to 200 (maximum). No, the levels are purely for developers -- i.e. look in the code. > Last thing: Is there a possibility to set a timestamp within traces? As I > saw in the test-output, there isnt one. Thats a big disadvantage if I want > to look for performance bottlenecks in the output. There is no documented way, but I think starting the daemons with -dt will turn on timestamps. __Martin ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
