Do not set the `logtostderr` GLOG flag just to be on the safe side (#73360)
Summary:
Pull Request resolved: https://github.com/pytorch/pytorch/pull/73360
Some (internal) PyTorch users use GLOG for their own logging purposes as well. Since the default setting is already to write to `stderr` anyways, let's be a good citizen and don't interfere with the logging settings of the main application.
ghstack-source-id: 149874118
Test Plan: Run existing unit and integration tests.
Reviewed By: zhaojuanmao
Differential Revision: D34452040
fbshipit-source-id: 1a6e1e94e25c3c50c82a2696548f7f08c0a9ee67
(cherry picked from commit 23741aa6f83f1dbbc627cc1428ae88d48f388688)
diff --git a/c10/util/Logging.cpp b/c10/util/Logging.cpp
index d0d0936..0e67632 100644
--- a/c10/util/Logging.cpp
+++ b/c10/util/Logging.cpp
@@ -224,9 +224,6 @@
} // namespace
void initLogging() {
- // Unlike caffe2 torch always writes to stderr.
- FLAGS_logtostderr = 1;
-
detail::setLogLevelFlagFromEnv();
UpdateLoggingLevelsFromFlags();
