Ciao Gregor, You're right: it's wired at server startup. I've introduced a new env variable to skip that part of code:
*java ... -Dorientdb.installCustomFormatter=false* It's in 2.0.1-SNAPSHOT. Please could you try it and confirm that works? Thanks, Lvc@ On 26 January 2015 at 17:21, Gregor Frey <[email protected]> wrote: > Hi, > actually I embed the OrientDB and have my own log-configuration file, > which is set with the system variable java.util.logging.config.file. > What happens is that as long as the OrientDB is not started, my Formatter > (actually the standard SimpleFormatter) is used, but as soon as the > dbserver is up, all logs on the console ignore my format. If I look into > the OLogManager I see that the OLogFormatter is set for each instance of > ConsoleLogger (line 65). That's why I said it is hard coded. At least my > log-configuration is overwritten. The orientdb-server-log.properties files > has no influence on this, because the system variable is set to my own > file. > Ciao > Gregor > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
