mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #1343] [MERGED] Moved the SIGUSR2 handler to S3fsSignals class #1929
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1929
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1343
Author: @ggtakec
Created: 7/26/2020
Status: ✅ Merged
Merged: 7/28/2020
Merged by: @gaul
Base:
master← Head:move_sigusr2📝 Commits (1)
ece7988Moved the SIGUSR2 handler to S3fsSignals class📊 Changes
3 files changed (+70 additions, -66 deletions)
View changed files
📝
src/s3fs.cpp(+8 -66)📝
src/sighandlers.cpp(+56 -0)📝
src/sighandlers.h(+6 -0)📄 Description
Relevant Issue (if applicable)
#1334
Details
Since a class summarizing the processing of the signal handlers has been added, the SIGUSR2 handler and its related processing have been moved to that class.
SIGUSR2 handler is set to bump up the debug log level.
Also, the debugging log level is set by a global variable(it is using a global variable because it is called from a macro in anywhere), but I also moved the operation function of this variable to that class.
Please note that the processing logic has not changed.
This will be a underplot as we will combine other signal handlers into S3fsSignals in the future.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.