[PR #275] [MERGED] Changed and cleaned the logic for debug message. #1440

New issue

Closed

opened 2026-03-04 01:53:58 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:53:58 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/275
Author: @ggtakec
Created: 9/30/2015
Status: ✅ Merged
Merged: 9/30/2015
Merged by: @ggtakec

Base: master ← Head: master

📝 Commits (1)

92e52da Changed and cleaned the logic for debug message.

📊 Changes

11 files changed (+733 additions, -620 deletions)

View changed files

📝 doc/man/s3fs.1 (+8 -0)
📝 src/cache.cpp (+6 -6)
📝 src/common.h (+85 -61)
📝 src/curl.cpp (+217 -179)
📝 src/curl.h (+2 -0)
📝 src/fdcache.cpp (+64 -64)
📝 src/gnutls_auth.cpp (+7 -7)
📝 src/nss_auth.cpp (+2 -2)
📝 src/openssl_auth.cpp (+6 -6)
📝 src/s3fs.cpp (+315 -284)
📝 src/s3fs_util.cpp (+21 -11)

📄 Description

Added new option "dbglevel" for debug message level.
Older version has only on/off for message, thus new one has critical/error/warning/info/debug mode.
The default level is critical.
And added signal handler for SIGUSR2, bumpup the debug level when s3fs catches this signal.

About message puts:
Older version could not put curl debug message and forground's message to syslog.
But new s3fs is able to put those.
If s3fs is run with "-f" option(means forground), all messages puts stdout and no message puts syslog.
The other without "-f"(means background), all messages puts syslog.
Then we can debug s3fs it runs background.(if you need to changeb debug level after starting s3fs, you can send SIGUSR2 to s3fs).

Then I hope this change helps us for debugging s3fs on background and at booting( like issue #273 ).

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/275 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 9/30/2015 **Status:** ✅ Merged **Merged:** 9/30/2015 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`92e52da`](https://github.com/s3fs-fuse/s3fs-fuse/commit/92e52dadd4ca3b84e8d7a347189737caa243f42d) Changed and cleaned the logic for debug message. ### 📊 Changes **11 files changed** (+733 additions, -620 deletions) <details> <summary>View changed files</summary> 📝 `doc/man/s3fs.1` (+8 -0) 📝 `src/cache.cpp` (+6 -6) 📝 `src/common.h` (+85 -61) 📝 `src/curl.cpp` (+217 -179) 📝 `src/curl.h` (+2 -0) 📝 `src/fdcache.cpp` (+64 -64) 📝 `src/gnutls_auth.cpp` (+7 -7) 📝 `src/nss_auth.cpp` (+2 -2) 📝 `src/openssl_auth.cpp` (+6 -6) 📝 `src/s3fs.cpp` (+315 -284) 📝 `src/s3fs_util.cpp` (+21 -11) </details> ### 📄 Description Added new option "dbglevel" for debug message level. Older version has only on/off for message, thus new one has critical/error/warning/info/debug mode. The default level is critical. And added signal handler for SIGUSR2, bumpup the debug level when s3fs catches this signal. About message puts: Older version could not put curl debug message and forground's message to syslog. But new s3fs is able to put those. If s3fs is run with "-f" option(means forground), all messages puts stdout and no message puts syslog. The other without "-f"(means background), all messages puts syslog. Then we can debug s3fs it runs background.(if you need to changeb debug level after starting s3fs, you can send SIGUSR2 to s3fs). Then I hope this change helps us for debugging s3fs on background and at booting( like issue #273 ). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>