ctubbsii commented on PR #2293: URL: https://github.com/apache/zookeeper/pull/2293#issuecomment-3186413064
> What does this mean for users of the clien lt library ? ZooKeeper clients will use whatever slf4j runtime is on their classpath, just as before. If they had included the `$ZOOKEEPER_TARBALL_DIRECTORY/lib` in that classpath before, then they would have automatically used the logback runtime library... but if they didn't have a logback configuration file, it would have done whatever logback defaulted to without a config. Now, it would pick up the slf4j-simple runtime, and log to the console, configurable with some [basic system properties](https://www.slf4j.org/api/org/slf4j/simple/SimpleLogger.html). If a different logging runtime is desired, the user would set their classpath appropriately to use the desired runtime library, and configure it according to their selected library. > What does this mean for system administrators of a server deployed from our tarball ? By default, they will use the slf4j-simple implementation jar in the `$ZOOKEEPER_TARBALL_DIRECTORY/lib` directory which will be on their classpath. If they want to use a different implementation, they will need to modify their CLASSPATH, which they can do in the `$ZOOCFGDIR/java.env` file or the `$ZOOCFGDIR/zookeeper-env.sh` file. If they want to keep slf4j-simple, but don't want the default behavior, they can set system properties in those files, by setting one of several different JVM flags environment variables (`SERVER_JVMFLAGS`, `CLIENT_JVMFLAGS`, the older `JAVA_TOOL_OPTIONS`, or the newer `JDK_JAVA_OPTIONS`, or the poorly documented `_JAVA_OPTIONS`) to include `-Dorg.slf4j.simpleLogger.logFile=` or similar system properties from the [`slf4j-simple` documentation](https://www.slf4j.org/api/org/slf4j/simple/SimpleLogger.html). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
